Jeremy Huntwork wrote: > LFS Trac wrote: >> Changes (by [EMAIL PROTECTED]): >> >> * resolution: => invalid >> * status: assigned => closed > > Out of curiosity, is there a reason to do it this way rather than just > change the summary? > > I agree that we shouldn't do what we used to do with Bugzilla and keep > using the same ticket for each package, opening and closing again > whenever there's a version upgrade (when it's closed, it's closed). But > in instances where the ticket hasn't even been touched and there's a new > version released in the meantime, any reason we can't just change the > summary?
Just for reference, the BLFS policy is: If there is a closed ticket, or none at all, for a package when a new version comes out, open a new ticket. If there is an open ticket for a package when a new version is released, modify the existing ticket. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-book FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
