Trac tickets ready for general use
Allison Randal
allison at parrot.org
Wed Nov 19 07:20:42 UTC 2008
Klaas-Jan Stol wrote:
>
> I think it's important to remember that the Parrot source has some
> references to RT # numbers. If a ticket is ported to trac, but the RT#
> is not updated in the source, it'll become painful to fix this later.
>
> This makes the porting process (converting RT tickets to trac) a bit
> less trivial. However, I think it's important to keep this in mind.
Yes, good point. Grepping through the repository for the ticket number
should be easy enough. For those who don't have commit access, it may be
more straight-forward to leave a closing comment in the old ticket with
a link to the new ticket (a good idea anyway). We'll need to do a review
of all RT links in source code before 1.0, which is a good time to
update any leftover indirect RT->Trac links to direct Trac links for the
ones we don't reject/delete.
BTW, if we standardize on either "ticket:4567" or "#4567" (maybe "Trac
#4567" or "TT #4567"), Trac will automatically turn those references in
commit messages into HTML links to the ticket, after we switch over to
svn.parrot.org.
Allison
More information about the parrot-dev
mailing list