*snip* Christian Boos wrote: > Jonas Borgström wrote: >> Since projects.edgewall.com needs to be functioning at all times the >> upgrade policy has always been to track the latest stable branch and >> only switch to trunk when we're close to a new stable release. >> So once we've made switch to trunk we have to stay there until a new >> stable branch has been cut. This is why switching p.e.c to trunk just >> for a "check point" is not such a good idea. > > When I asked for it, 0.10dev was indeed stabilized, and already running > on trac-hacks > without much trouble. > We where "mid-way" on the long list of 0.10 features, so I still think > it would have > been a good idea to get that version running on p.e.c, because when we > switched > to 0.10dev later, we had not only those features, but also the WSGI and > unicode > changes, so it was potentially more disruptive.
Yeah, but _if_ we switch to trunk in the middle of a release cycle just because it looked "stable" for the moment we risk getting stuck with that revision for a long time since trunk can quickly become unstable again when large changes like WSGI or unicode are landed and we can't go back to x.y-stable either because of obvious reasons... So imho. it's better to keep using a stable branch until trunk "seems stable" _and_ no more major changes are planned until the next stable release. > >> But I still never heard >> your query about upgrading to trunk in January... >> > > Well, it was actually the 1st of February, as 2/1/2006 is easy to confuse > with the 2nd of January, for a french reader :) > I asked a second time the 17th... then I gave up. > Ok, I'm sorry about that, I'm not always able to read all postings on the lists :( > http://thread.gmane.org/gmane.comp.version-control.subversion.trac.devel/136/focus=136 > > http://article.gmane.org/gmane.comp.version-control.subversion.trac.devel/206 > > >> Which InterTrac aliases are you interested in? >> > > Please check > http://thread.gmane.org/gmane.comp.version-control.subversion.trac.devel/306/focus=313 > ok, done. > >> Regarding the revision p.e.c is running, a good solution would be to >> hack the about page to show the revision next to the version number. >> Is that a good enough solution? >> > > What about simply editing the current Milestone description? > > Revision log: ... > Currently running r32xx. > > -- Christian > > > _______________________________________________ > Trac-dev mailing list > [email protected] > http://lists.edgewall.com/mailman/listinfo/trac-dev _______________________________________________ Trac-dev mailing list [email protected] http://lists.edgewall.com/mailman/listinfo/trac-dev
