David Cournapeau (el 2008-01-04 a les 20:24:04 +0900) va dir:: >[...] > Integration with trac is the real problem, I think. According to one bzr > developer, trac model (0.10, the last released one) is really based > around subversion notion of repository, which does not fit well with > mercurial and bzr. I don't know if this is true for the not yet released > 0.11. If bzr is considered a possible candidate, I can get more > informations from bzr developers. >[...]
My main concern about Trac and bzr integration is that (please correct
me if I'm wrong or outdated) Trac doesn't seem to support multiple
bzr branches, even if they are under the same shared repository. This
would limit Trac to following only one bzr branch, say the trunk
(leaving tags and branches out of its control). If this was to be
avoided by creating a single bzr branch with all branches and tags, we
may be facing a size problem, since bzr lacks cheap copying operations
right now (but support is planned). Anyway, this last approach isn't
very appropriate with a DVCS.
(Multiple bzr branch support in Trac would be really wonderful!)
::
Ivan Vilata i Balaguer >qo< http://www.carabos.com/
Cárabos Coop. V. V V Enjoy Data
""
signature.asc
Description: Digital signature
_______________________________________________ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
