Hello Dave!
I think the persons working with the project can decide this on a per
project basis, as described in the Cookbook section 2.6.2.2.
I think that the recommendation is that they decide to use the issuezilla in
the main project. The Cookbook could be improved to describe this.
If you don't know what issuezilla you should use, the Issues link in the
Project tools should point to the one decided on in that project.
I can think of the following pros and cons:
- Use of the project issuezilla allows developers interested in a certain
project to subscribe to the corresponding mailing list for notifications on
issues without getting notifications of all issues.
- Use of the project issuezilla allows a different notification policy
(sending mails when issues are getting old).
- Use of the argouml issuezilla simplifies the handling of versions and
milestones. (I have not created them anywhere but in the ArgoUML project
because it is extra work).
- Use of the argouml issuezilla increases the visibility of the issue for
the rest of the argouml project.
/Linus
2008/5/16, Dave Thompson <[EMAIL PROTECTED]>:
>
> Hi,
>
> This is probably a question for Linus. Should we ever be using issue
> trackers on subprojects, or should we always use the main argouml
> project one? I notice that there are a lot of subprojects listed as
> components on the main project issue tracker. Does this imply that we
> should submit issues there?
>
> I've got some issues relating to the argoumlinstaller project, and am
> wondering whether to submit them on the subproject's own issue tracker
> (which currently has a total of 6 issues), or on the main argouml issue
> tracker.
>
> Regards,
>
> Dave
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
