[Debian] Debian squeeze is frozen [neilm@debian.org: Bits from
the (chilly) release team]
Ola Lundqvist
ola at inguza.com
Sat Aug 7 16:50:11 EDT 2010
Hi Kir
On Sat, Aug 07, 2010 at 01:34:36PM +0400, Kirill Kolyshkin wrote:
> Ola,
>
> Thanks for good news and for your work. Was that release 3.0.24 or
> 3.0.24.1?
3.0.24 I was not aware you had made a 3.0.24.1. Is it something important
that I should try to get into squeeze?
Best regards,
// Ola
> sent from my google nexus one android mobile phone
>
> On Aug 7, 2010 12:23 PM, "Ola Lundqvist" <[1]opal at debian.org> wrote:
> > Hi Kir and others
> >
> > I quite from below:
> >
> > "In other words, Squeeze has frozen. Thanks are due to everyone who
> has
> > helped get us to this point."
> >
> > Just thought you should know. I was a bit lucky to get the latest
> vzctl
> > release in before the freeze. :-) Phew.
> >
> > Best regards,
> >
> > // Ola
> >
> > ----- Forwarded message from Neil McGovern <[2]neilm at debian.org>
> -----
> >
> > Envelope-to: [3]ola at inguza.com
> > Delivery-date: Fri, 06 Aug 2010 15:55:18 +0200
> > Old-Return-Path: <[4]maulkin at halon.org.uk>
> > X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on
> [5]liszt.debian.org
> > X-Spam-Level:
> > X-Spam-Status: No, score=-7.7 required=4.0 tests=FVGT_m_MULTI_ODD,
> > IMPRONONCABLE_2,LDO_WHITELIST,MURPHY_DRUGS_REL8,MURPHY_FINANCE11,
> > MURPHY_WRONG_WORD1,MURPHY_WRONG_WORD2,PGPSIGNATURE autolearn=failed
> > version=3.2.5
> > X-Virus-Scanned: at [6]lists.debian.org with policy bank moderated
> > X-Amavis-Spam-Status: No, score=-7.66 tagged_above=-10000
> required=5.3
> > tests=[FVGT_m_MULTI_ODD=0.02, IMPRONONCABLE_2=1, LDO_WHITELIST=-5,
> > MURPHY_DRUGS_REL8=0.02, MURPHY_FINANCE11=1, MURPHY_WRONG_WORD1=0.1,
> > MURPHY_WRONG_WORD2=0.2, PGPSIGNATURE=-5] autolearn=ham
> > X-policyd-weight: using cached result; rate:hard: -6.2
> > X-Greylist: delayed 586 seconds by postgrey-1.31 at liszt; Fri, 06
> Aug 2010 13:54:14 UTC
> > From: Neil McGovern <[7]neilm at debian.org>
> > To: [8]debian-devel-announce at lists.debian.org
> > Subject: Bits from the (chilly) release team
> > Mail-Followup-To: [9]debian-devel-announce at lists.debian.org
> > X-Debian-Message: Signature check passed for Debian member
> > X-Rc-Spam: 2008-11-04_01
> > Resent-Message-ID: <8fJxHHdhzK.A.giH.ZQBXMB at liszt>
> > Resent-From: [10]debian-devel-announce at lists.debian.org
> > X-Mailing-List: <[11]debian-devel-announce at lists.debian.org>
> archive/latest/1279
> > List-Id: <[12]debian-devel-announce.lists.debian.org>
> > List-Post: <mailto:[13]debian-devel-announce at lists.debian.org>
> > List-Help:
> <mailto:[14]debian-devel-announce-request at lists.debian.org?subject=help
> >
> > List-Subscribe:
> <mailto:[15]debian-devel-announce-request at lists.debian.org?subject=subs
> cribe>
> > List-Unsubscribe:
> <mailto:[16]debian-devel-announce-request at lists.debian.org?subject=unsu
> bscribe>
> > Resent-Sender: [17]debian-devel-announce-request at lists.debian.org
> > Resent-Date: Fri, 6 Aug 2010 13:54:33 +0000 (UTC)
> > X-Spam-Score: -1.0 (-)
> > X-Spamcheck-provider: Checked for spam by [18]inguza.net,
> [19]postmaster at inguza.net
> >
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA256
> >
> > Hi,
> >
> > As I'm writing this mail, Adam D. Barratt (adsb) is currently giving
> a
> > presentation at Debconf about "Bits from the Release Team". This is
> the
> > mail version for those who can't make it to New York. It contains
> some
> > important information, so please read it through to the end!
> >
> > Team membership changes
> > =======================
> >
> > After a little absence of formal release managers, we're pleased to
> > announce that Adam and myself are the new Release Managers.
> > Additionally, Luk Claes is now a Release Wizard. Myself and the rest
> of
> > the team would like to take this opportunity to thank Luk for his
> years
> > of hard work which has certainly improved Debian in immesureable
> ways.
> >
> > We are still looking for enthusiastic DDs who would be interested in
> > joining the team and helping us to make Squeeze the great release we
> all
> > believe it can be. If you're interested, please contact us at
> > [20]debian-release at lists.debian.org or on #debian-release.
> >
> > Current status
> > ==============
> >
> > As mentioned in the previous mail, we would freeze when various
> > transitions are completed or being handled. We now feel that this
> stage
> > has been reached. This means that we have stopped the automatic
> > migration of packages from unstable to testing.
> >
> > In other words, Squeeze has frozen. Thanks are due to everyone who
> has
> > helped get us to this point.
> >
> >
> > Perhaps that's too subtle:
> > _==_ _
> > _,(",)|_| *** Frosty says Squeeze is FROZEN. ***
> > \/. \-| (He's in Austrailia, as it's winter there -
> > __( : )|___ that's what the shovel is for, sandcastles)
> >
> >
> > Don't Panic!
> > ============
> >
> > Even though Squeeze has frozen, that doesn't mean it's impossible to
> get
> > your changes into Squeeze.
> >
> > Now to explain what, exactly, we mean by "freeze". The freeze upload
> > policy of uploading changes in through unstable if possible will be
> > continued to apply until the release.
> >
> > Packages that are present in unstable today will be automatically
> > allowed into testing; this does not mean your package should be in
> > testing by now, but only in unstable.
> >
> > If your package has a particular change that you feel really, really
> > needs to make the release, talk to us and we can discuss it.
> >
> > What now?
> > =========
> >
> > Now, so as not to have everyone contact us at once about packages we
> > know we won't approve, here are the guidelines for changes that will
> be
> > accepted into testing during the freeze:
> >
> > - fixes for release critical bugs (i.e., bugs of severity critical,
> > grave, and serious) in all packages;
> >
> > - changes for release goals, if they are not invasive;
> >
> > - fixes for severity: important bugs in packages of priority:
> optional
> > or extra, only when this can be done via unstable;
> >
> > - translation updates and
> >
> > - documentation fixes.
> >
> > - pre-approved fixes.
> >
> > - as above, important changes that the maintainer feels are *NEEDED*
> > before release
> >
> > If you have such a change and want to update your package in squeeze,
> the
> > rules are as follows:
> >
> > - In all cases, when preparing an upload, please do not make changes
> to
> > the package that are not related to fixing the bugs in question.
> > Doing so makes it more time consuming for the release team to review
> > and approve such requests, delaying the release. It also delays the
> > fix for your package, because you will be asked to reupload. Always
> > document every change verbosely in the changelog.
> >
> > - If in doubt, first contact debian-release.
> >
> > - When contacting the release team, please explain why you are
> > requesting an update. Bug numbers are a must. Attach the proposed
> > (or uploaded) patch. The more we can figure out from your first email
> > and your changelog (if any), the more quickly we can get your update
> > in.
> >
> > - If your package needs to be updated for Squeeze, and the version in
> > unstable doesn't contain extraneous changes (e.g, the version is the
> > same between testing and unstable), please upload your fix to
> > unstable and contact [21]debian-release at lists.debian.org.
> >
> > - If the version in unstable already includes significant changes not
> > related to the bug to be fixed, contact debian-release about
> > uploading to testing-proposed-updates. Changed dependencies, new
> > upstream versions, changed library names, and completely rewriting
> > the packaging are "significant changes". So are lots of other
> > things.
> >
> > - If the version in unstable won't reach testing because of new
> > library dependencies, contact debian-release about uploading to
> > testing-proposed-updates.
> >
> > - If you have a package that needs a freeze exception, *please* don't
> > forget to contact us. *Don't expect us to find out about it on our
> > own*. Putting a comment in the changelog is not contacting the
> > release team. :)
> >
> > - If your package has been removed recently (i.e. in the last 20
> days)
> > due to an RC bug, and you have an bugfix-only update uploaded,
> > you can contact the release team about letting your package back in.
> > Same as above: Do not expect us to find it out ourselves. You need to
> > push that.
> >
> >
> > As always, it is the release team's goal to get as much good software
> > into Squeeze as possible. However, a freeze does not mean that your
> > package is ensured a spot in the release. Please continue to stay on
> > top of release-critical bugs in packages that you maintain; RC bugs
> in
> > optional or extra packages that remain unfixed after a week will
> still
> > be grounds for removal from testing. Please also try and encourage
> > packages you depend on with RC bugs. We'd like to avoid removing lots
> of
> > packages with dependencies if possible, and your help can be
> valuable.
> >
> > Please also note that since many updates (hopefully, the vast
> majority)
> > will still be going in through unstable, major changes in unstable
> right
> > now can disrupt efforts to get RC bugs fixed. We don't ask you not to
> > make changes in unstable, but we do ask that you be aware of the
> effects
> > your changes can have -- especially if you maintain a library. Please
> > continue to keep disruptive changes out of unstable, and continue
> making
> > use of experimental where appropriate. Note that you can stage NEW
> uploads
> > in experimental to avoid disruption in unstable.
> >
> > Also, in case you need the release team's help to fix RC bugs (e.g.
> to remove
> > an old package), please feel free to contact us.
> >
> > For packages which missed the freeze only for reasons outside of the
> > control of the maintainers, we might be generous, but you need to
> contact
> > us on your own, and you need to contact us soon.
> >
> > RC bugs
> > =======
> >
> > For the release, we need to get rid of all release critical bugs.
> Please
> > don't hesitate, pick any bug from
> > [22]http://bts.turmzimmer.net/details.php?bydist=squeeze and fix it.
> Or send in a
> > patch in case there is none yet. And of course, follow our permanent
> BSP
> > policy for your NMUs. Uploading works as you are used to -- just
> remember to
> > send an e-mail to [23]debian-release at lists.debian.org to get your fix
> through.
> >
> >
> > Thanks,
> > Neil McGovern
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.4.10 (GNU/Linux)
> >
> > iQIcBAEBCAAGBQJMW3daAAoJEMXOXcLFQs1Ze2QP/2RnhfRgAO8Jej8Osp9RgS4B
> > /0kM/2aSVbFQgKPTSxfUb8/xIAchJRh9fNdqWUIh4HKBD/UvXqR4ziDcR2hVJAHQ
> > H72TksC5/JP+3xCfKesOnj6/aDAe4kHDIn/xGnG3l+wUlAIdoEgmX1vlDiCg9Rlg
> > VN8Od2I1L+7cFIeJ/RLD0tdirpM/Z4sKVVPAlRQX1oQ2e8SsrvbdyxWBnnl27Mo5
> > wQ874nUurKlJzSG231QY3IWt9HYCjy1VYJTAxwvmu3D2ZzDT1s+r21q3nh01s4pJ
> > 93OQgyG6NoodciJUfWQ4cv9NaJ1/7aq4DblxSDvdeMXJqmVvRcaEdQi1J5KcxDK0
> > 329snmuZh98EDteJ5nPNNR6cpJoZU45P9X2KVVh2j2t55UJVGn8usyjW1H/QVYXo
> > ZZfgHAee1GPCCITHXFvmKcOfYjSFLytkecC536TAb2fLcSjHBRNen5XC1yVkxrdC
> > yamTLpu0XkHJW/wBmrnAh/Zru0onoBPSoeLpN1pK4zFkg//IAU0wigSnCTx7rpYS
> > UfjqicNCjimxekpCtEEvCdmAADXugxkG3CVmJ2UC+5VWPwLI6ZAtzvUQg7ipXgAP
> > 0UbLsqd7aBYdtWkWZDsU5ln1lM5A5JEh3TwYcQtQ7s/6HKdqeBh+JDxKMSv0RVQL
> > fgQIflockyv3+SJ/dPCh
> > =N/Yn
> > -----END PGP SIGNATURE-----
> >
> >
> > --
> > To UNSUBSCRIBE, email to
> [24]debian-devel-announce-REQUEST at lists.debian.org
> > with a subject of "unsubscribe". Trouble? Contact
> [25]listmaster at lists.debian.org
> > Archive:
> [26]http://lists.debian.org/20100806134418.GC9183@halon.org.uk
> >
> >
> >
> > ----- End forwarded message -----
> >
> > --
> > --------------------- Ola Lundqvist ---------------------------
> > / [27]opal at debian.org Annebergsslingan 37 \
> > | [28]ola at inguza.com 654 65 KARLSTAD |
> > | [29]http://inguza.com/ +46 (0)70-332 1551 |
> > \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 /
> > ---------------------------------------------------------------
> > _______________________________________________
> > Debian mailing list
> > [30]Debian at openvz.org
> > [31]https://openvz.org/mailman/listinfo/debian
>
> Referenser
>
> 1. mailto:opal at debian.org
> 2. mailto:neilm at debian.org
> 3. mailto:ola at inguza.com
> 4. mailto:maulkin at halon.org.uk
> 5. http://liszt.debian.org/
> 6. http://lists.debian.org/
> 7. mailto:neilm at debian.org
> 8. mailto:debian-devel-announce at lists.debian.org
> 9. mailto:debian-devel-announce at lists.debian.org
> 10. mailto:debian-devel-announce at lists.debian.org
> 11. mailto:debian-devel-announce at lists.debian.org
> 12. http://debian-devel-announce.lists.debian.org/
> 13. mailto:debian-devel-announce at lists.debian.org
> 14. mailto:debian-devel-announce-request at lists.debian.org
> 15. mailto:debian-devel-announce-request at lists.debian.org
> 16. mailto:debian-devel-announce-request at lists.debian.org
> 17. mailto:debian-devel-announce-request at lists.debian.org
> 18. http://inguza.net/
> 19. mailto:postmaster at inguza.net
> 20. mailto:debian-release at lists.debian.org
> 21. mailto:debian-release at lists.debian.org
> 22. http://bts.turmzimmer.net/details.php?bydist=squeeze
> 23. mailto:debian-release at lists.debian.org
> 24. mailto:debian-devel-announce-REQUEST at lists.debian.org
> 25. mailto:listmaster at lists.debian.org
> 26. http://lists.debian.org/20100806134418.GC9183@halon.org.uk
> 27. mailto:opal at debian.org
> 28. mailto:ola at inguza.com
> 29. http://inguza.com/
> 30. mailto:Debian at openvz.org
> 31. https://openvz.org/mailman/listinfo/debian
--
--- Inguza Technology AB --- MSc in Information Technology ----
/ ola at inguza.com Annebergsslingan 37 \
| opal at debian.org 654 65 KARLSTAD |
| http://inguza.com/ Mobile: +46 (0)70-332 1551 |
\ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 /
---------------------------------------------------------------
More information about the Debian
mailing list