There are some features I'd really like to make use of in 0.11, particularly the metrics feature, but I think there are others as well. Trac 0.11 is where all the development seems to be happening, we'll slowly fall farther and farther behind.
There is a catch with 0.11, in that it requires an ondisk change of the project db, so I don't feel comfortable just putting 0.11 in EPEL-5 as an upgrade to 0.10.
What I'd like is some help in investigating and planning how to do the upgrade in such a way that will be a low cost to the Infra team to maintain, but could also perhaps be pushed into EPEL for other trac users.
Would anybody like to help me with this?
On Sun, 2009-02-01 at 22:17 -0800, Jesse Keating wrote:
There are some features I'd really like to make use of in 0.11, particularly the metrics feature, but I think there are others as well. Trac 0.11 is where all the development seems to be happening, we'll slowly fall farther and farther behind.
There is a catch with 0.11, in that it requires an ondisk change of the project db, so I don't feel comfortable just putting 0.11 in EPEL-5 as an upgrade to 0.10.
What I'd like is some help in investigating and planning how to do the upgrade in such a way that will be a low cost to the Infra team to maintain, but could also perhaps be pushed into EPEL for other trac users.
Would anybody like to help me with this?
I'm willing to help, but I have to ask - would it make sense to hold this until after F11 is out?
-sv
On Mon, 2009-02-02 at 08:36 -0500, seth vidal wrote:
I'm willing to help, but I have to ask - would it make sense to hold this until after F11 is out?
I don't necessarily think so. If done right, the change is pretty unnoticeable to the end user, just one day they get more features. I think the only real risk wrt F11 is me spending too much time on Trac, which is why I'm asking for some help (:
On Mon, 2 Feb 2009, Jesse Keating wrote:
On Mon, 2009-02-02 at 08:36 -0500, seth vidal wrote:
I'm willing to help, but I have to ask - would it make sense to hold this until after F11 is out?
I don't necessarily think so. If done right, the change is pretty unnoticeable to the end user, just one day they get more features. I think the only real risk wrt F11 is me spending too much time on Trac, which is why I'm asking for some help (:
After the alpha ships we can do a test upgrade on hosted2 for a project. If the tests and everything go ok we can do the rest and verify the upgrade produces no errors and warnings. The last upgrade was very smooth. It was pretty much a
for f in * do the upgrade done
-Mike
On Mon, 2009-02-02 at 11:11 -0600, Mike McGrath wrote:
After the alpha ships we can do a test upgrade on hosted2 for a project. If the tests and everything go ok we can do the rest and verify the upgrade produces no errors and warnings. The last upgrade was very smooth. It was pretty much a
for f in * do the upgrade done
We'll have to do some pre work, building trac-0.11 and then building any plugins that are still 3rd party for 0.11 as well.
On Sun, 1 Feb 2009, Jesse Keating wrote:
There are some features I'd really like to make use of in 0.11, particularly the metrics feature, but I think there are others as well. Trac 0.11 is where all the development seems to be happening, we'll slowly fall farther and farther behind.
There is a catch with 0.11, in that it requires an ondisk change of the project db, so I don't feel comfortable just putting 0.11 in EPEL-5 as an upgrade to 0.10.
What I'd like is some help in investigating and planning how to do the upgrade in such a way that will be a low cost to the Infra team to maintain, but could also perhaps be pushed into EPEL for other trac users.
Would anybody like to help me with this?
I can help with this, I've gone through a trac upgrade that required on disk changes before, hosted2 makes testing pretty easy :)
-Mike
infrastructure@lists.fedoraproject.org
-
Jesse Keating -
Mike McGrath -
Seth Vidal