On Mon, Nov 28, 2005 at 01:02:51PM +0000, Julian Gilbey wrote: > On Sun, Nov 27, 2005 at 10:25:23PM -0600, Peter Samuelson wrote: > > > > [A Mennucc] > > I don't like the idea of encouraging people to fit the reason for > > closing a bug onto a single line. > > I was thinking of something like: > bts done #bugnumber #version > opening an editor to enter the comment.
sounds nice (and it is similar to the way 'svn commit' or 'cvs commit' work) also, "bts done #bugnumber" would ask for a version if it was not provided and the package is not virtual (and check that the version is sensible, so avoiding that people would fall in a mess as in bug 337667 ) The point is, the proper use of the "Version:" pseudo-header is best documented in footnote 2 in http://lists.debian.org/debian-devel-announce/2005/10/msg00006.html and that is not a place people will easily look at. I acknowledge that http://www.debian.org/Bugs/Developer talks about the "Version:" pseudo-header, but it is too abstract, and people may misunderstand it, may forget about it , or downplay the importance of it. Whereas a command such as "bts done #bugnumber" would guide the user in using the "Version:" pseudo-header. After all, that is the reason why I (we) prefer to use "reportbug" for reporting, and "bts" for managing: because they help doing the best job. btw: it all started when zope2.7 2.7.5-2sarge1 was accepted in sarge-security, and indeed the changelog did not contain a proper "Closes: nnn": I wanted to add "fixed: 2.7.5-2sarge1" it took me quite some time to find how; you see, when you are looking for a way to alter a "fixed" tag, you look for a "fixed" command, and the "fixed" command is not everywhere to be found. It took me quite some googling to find http://lists.debian.org/debian-devel-announce/2005/10/msg00006.html So "bts fixed" may be an alias for "bts done" a. -- Andrea Mennucc "Ukn ow,Ifina llyfixe dmysp acebar.ohwh atthef" -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
