Announcing Cart

Alexander Belchenko bialix at ukr.net
Wed Oct 3 13:08:19 BST 2007


Aaron Bentley пишет:
> Alexander Belchenko wrote:
>>> - no wiki functionality (unless someone can explain why it belongs there)
>> I found wiki is really powerful part of Trac. E.g. in my company we
>> keep [almost] all project documentation in wiki. It's very useful.
> 
> Sure, but does it work better or worse than Moin?  I've never seen big
> benefits from the fact that the wiki's part of the same package as the
> bug tracker and source viewer.

I like Trac wiki because I don't need to install Moin. It's all in one,
and works together very well, as Lalo said. Also it's nice to use
wiki-markup in bug reports and roadmap descriptions.

BTW, what about roadmap? I found it very very very important to
track progress when team working for several customers/several goals
during long time.

> One thing I'm thinking about is having Cart generate documentation from
> source code, the way we do manually on http://doc.bazaar-vcs.org/ and
> with a similar goal of presenting documentation for the various releases.

Yeah, that will be great.
I keep all my documentation in ReST in separate bzr branch, but Trac 
wiki beats this approach because it's easier, and regeneration of docs 
done after each "commit" automatically.

>>> - Branches and tickets may belong to "subprojects", which are used for
>>> grouping purposes.  In the Bazaar project, bzr might be one subproject,
>>> and bzr-gtk might be another.
>> What about hierarchical bugs?
> 
> I'm planning to support dependencies for bugs.  Is this something else?

I think it's the same thing.
I mean this: in our project we have many components working together. 
And sometimes to fix the bug means fix it in several different branches.
And sometimes several different people work on different branches.
I'd like to have a way to split one bug report for several people,
several branches.
So we talk about the same thing here?



More information about the bazaar mailing list