On 2/3/2010 10:14 AM, Remy Blank wrote:
Christian Boos wrote:
I've some ideas regarding the concerns expressed by osimons in the other
mail about explicit vs. implicit resync and IRepositoryChangeListener,
but this shouldn't delay the merge.
Yes, I'm also interested in finding a better / alternative solution. The
hooks are a bit of a pain, and platform-specific on top of that.
So today should be a good day for the merge:
http://trac.edgewall.org/timeline?from=2008-02-03T21:19:53%2B01:00&precision=second
i.e. exactly 2 years after the announcement of the branch ;-)
A good day indeed. Happy birthday!
It's done! See tr...@9125.
The TracMercurial plugin for 0.12 has also been upgraded to be the same
as the former one for multirepos:
http://trac.edgewall.org/browser/plugins/0.12/mercurial-plugin?rev=9129
For people going to upgrade, please have a look at:
http://trac.edgewall.org/wiki/0.12/TracUpgrade#UpgradingtoTrac0.12
There's a need to do a `trac-admin ... upgrade`, as the database model
has changed.
Doing a `trac-admin ... wiki upgrade` is also a good idea, as quite a
few documentation pages have been updated.
In particular, the new
http://trac.edgewall.org/wiki/0.12/TracRepositoryAdmin page describes in
more details all what you need to know about multiple repository support.
I guess we should finish to update the TracDev/ApiChanges/0.12 to
reflect what has changed in trac.versioncontrol API. In any case, I'm
interested in getting the feedback from IRepositoryConnector plugin
developers, to know which ones currently support the multirepos feature
and if there's any issue left for them.
-- Christian
--
You received this message because you are subscribed to the Google Groups "Trac
Development" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/trac-dev?hl=en.
