Announcing Cart
Aaron Bentley
aaron.bentley at utoronto.ca
Wed Oct 3 13:50:20 BST 2007
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Alexander Belchenko wrote:
> Aaron Bentley пишет:
> 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.
I already have Moin set up, so this is not going to be a high priority
for me. But we already have some in-house ReST-wiki code that we could
potentially reuse.
> Also it's nice to use
> wiki-markup in bug reports and roadmap descriptions.
I plan to support ReST for bug reports and other text areas.
> 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.
We can support that. Cart will deal with "issues", which can be *bugs*,
*feature requests* or *tasks*. Perhaps *milestone* can be another kind
of issue, and then we can use issue dependencies to associate bugs with
them.
>> 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.
I'm not sure whether you really think it's a good idea, since you say
"Trac wiki beats this approach".
> 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.
Right. I think bug dependencies will work well as the underlying
representation. If one bug affects "backend" and "ui", you can have
three bugs: a "backend" bug, a "ui" bug, and a meta-bug that depends on
the "backend" and "ui" bugs.
> So we talk about the same thing here?
I think so.
Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHA5AL0F+nu1YWqI0RAplPAKCFNg9ylqNlXh3LM5OHLzk/Tde3GgCeIcmE
PzS9FpgXtRy0+Xt5KXgaIRY=
=lobP
-----END PGP SIGNATURE-----
More information about the bazaar
mailing list