On Mon, 1 Oct 2012 20:44:39 -0400 Albert Huang <alberth.debian@gmail.com> wrote: > > 5. as above, important changes that the maintainer feels are needed > > before release. > > > > http://release.debian.org/wheezy/freeze_policy.html > My intent was based on #5 - the current package(s), as they stand, are > rather unusable. ... but no bugs have been reported about such problems and it is too late to introduce a new package into Wheezy. The changes would have to be ported to the existing packages instead. > > None of which are release critical for Debian. > Ah - I originally thought that FTBFS was considered RC. Not unless the FTBFS affects a release architecture. > For backports, would I ask end users to add that repo once the release > occurs? To go into backports, the packages have to be first uploaded to unstable, migrated into testing (which will be Jessie by that stage) and then built on Wheezy and uploaded to wheezy-backports once that becomes available. > And backports will NOT ever migrate packages to stable > (wheezy), I would assume? Yes. backports never make it into a point release and these packages do not sound like they would be suitable for inclusion into a point release of Wheezy. Users of stable are generally quite familiar with using the relevant backports packages. Users specify exactly which packages are selected from backports. -- Neil Williams ============= http://www.linux.codehelp.co.uk/
Attachment:
pgpJzyyIpkQaA.pgp
Description: PGP signature