Re: Release update: minor delay; no non-RC fixes; upgrade reports
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
"Roberto C. Sanchez" <roberto@familiasanchez.net> writes:
> On Mon, May 30, 2005 at 12:59:26PM +0200, Adrian Bunk wrote:
>>
>> Finding these issues is one of the prices for freezing testing
>> instead of unstable [1].
>
> CMIIW, but isn't unstable a place where architectures can be out of
> sync? To get into a testing, a package has to pass the cooling off
> period with no >important bugs and must be in sync on all
> architectures. Correct? Freezing unstable doesn't make much sense
> if it means lots of extra work just to sync up package versions
> across architectures. The only that would work is to require that
> packages successfully build on all architectures *prior* to being
> admitted to the archive.
I think this misses the point. Consider a package present in both
testing and unstable, and later it has an RC bug filed against it,
which is subsequently fixed by an upload to unstable. The bug is
closed, but it's still present in testing. There's currently no way
to automatically and easily find these bugs. Thus there may be many
RC bugs in testing of which there is no trace in the BTS.
After testing freezes, we need a way of saying ("we need fixes x, y
and z from unstable to fix these unfixed RC bugs in testing").
This is at least how I understand what Adrian is saying. It's
something I hadn't considered before, and certainly deserves serious
consideration.
The BTS does not currently support this. For example, if I upload a
fix to unstable, I have to manually reopen it and tag it sarge.
Regards,
Roger
- --
Roger Leigh
Printing on GNU/Linux? http://gimp-print.sourceforge.net/
Debian GNU/Linux http://www.debian.org/
GPG Public Key: 0x25BFB848. Please sign and encrypt your mail.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>
iD8DBQFCmywlVcFcaSW/uEgRAvJsAJ9x3vHEHtjfVaqUz5R5w7od0AhD6ACfZa8+
BIn4zRHMM93rPL00ZLAPPJU=
=w+hP
-----END PGP SIGNATURE-----
Reply to: