Jonas Borgström wrote:
Christian Boos wrote:
Emmanuel Blot wrote:
Hi,
Is there a way to get notified when p.e.c. is updated with the trunk ?
I think it would be useful to post a notification (to trac-dev or
through a long-lasting ticket) to other developers, with the actual
revision that p.e.c. is running.
+1
... and a more "community friendly" way to run the Trac site would be
appreciated as well. For instance, my queries to upgrade to 0.10dev
in January have been ignored, though it would have been good to have
a check point at that time (before the unicode merge), my repeated
queries to add some intertrac links have been ignored as well, etc.
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.
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.
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
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
