[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: How to define a release architecture


On Tue, Mar 22, 2005 at 09:12:45AM +0100, Benjamin Mesing wrote:

> Why not freeze the archive at a given time and make a release for all
> architectures ready until then. As this code is frozen, the porters can
> continue to work on the frozen codebase where only patches are allowed
> which are needed fix the packages for the different architectures. This
> seems to be the same the security team currently does. The ported
> architectures would become available as soon as a new revision is
> released (of course this should happen as soon as a new arch has caught
> up).

For examples of why allowing release-candidate architectures to catch up
with the archive *after* freezing is a potential problem, please see the
following RC bugs in base packages that are going to result in the sarge
freeze period being the one and only testing cycle for detecting (possibly
architecture-specific) regressions:

  292673 297769 284961 291386 294404

Steve Langasek
postmodern programmer

Attachment: signature.asc
Description: Digital signature

Reply to: