Re: testing-stable-unstable [was: Are there too many Debian developers]
- To: firstname.lastname@example.org
- Subject: Re: testing-stable-unstable [was: Are there too many Debian developers]
- From: Bdale Garbee <email@example.com>
- Date: Mon, 16 Dec 2002 23:15:58 -0700
- Message-id: <[🔎] firstname.lastname@example.org>
- In-reply-to: <[🔎] 20021217050846.GA15412@mizar.alcor.net> (email@example.com's message of "Tue, 17 Dec 2002 05:09:11 +0000 (UTC)")
- References: <OF184EFD11.6AEC20B5-ON86256C8C.005C25EE@norlight.com> <20021211193929.GA16925@netexpress.net> <20021211231729.GA23676@home.ouaza.com> <20021212012656.B24788@gandalf.drinsama.de> <20021212082559.GA10638@zombie.inka.de> <20021212103122.GB2342@riva.ucam.org> <20021212165506.GE29455@mizar.alcor.net> <20021216111527.GA3244@asgard.pte.at> <20021216134454.GB26499@mizar.alcor.net> <20021216234754.GC17691@megafauna.finbar.dyndns.org> <[🔎] 20021217050846.GA15412@mizar.alcor.net>
firstname.lastname@example.org (Matt Zimmerman) writes:
> ... In order to accurately keep track of when the
> bugfixes propagate, the version information must be stored.
> This may be overkill for the general BTS, but I think it is important for
It's pretty clear that making it possible for the BTS to record a range of
versions for which a bug exists in a package is a good idea for a number of
reasons. I'd love to see a good general implementation.