I agree with Ryan, but are you also saying you also keep them "open"? Is there a reason for having multiple tickets open for the same issue?

-Bill




On Jan 17, 2008, at 9:51 PM, Ryan Schmidt wrote:


On Jan 17, 2008, at 23:46, Juan Manuel Palacios wrote:

Some of us are clashing on Trac: in one corner, those who keep duplicate tickets and/or set them to appropriate milestones; in the other corner, those (read, only me, I think) who take them out of milestones when encountering them.

The way I see it, if the ticket is a duplicate of an "original" one, and said original is already properly milestoned, then what's the benefit of also having the duplicate in the same milestone? And if said original is *not* properly milestoned, then it should be ;-)

But that's of course only one side of the ring. What does the other side have to say about it?

Why shouldn't all tickets (even duplicate tickets) have the correct milestone?



_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo/macports-dev




----
William Siegrist
Software Support Engineer
Mac OS Forge
http://macosforge.org/
[EMAIL PROTECTED]
408 862 7337





Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo/macports-dev

Reply via email to