public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev]  Re: stabilizing expat 2.0.0
Date: Thu, 17 May 2007 14:05:17 -0700	[thread overview]
Message-ID: <1179435917.25168.10.camel@workbox.quova.com> (raw)
In-Reply-To: <464CA00D.9080102@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 2350 bytes --]

On Thu, 2007-05-17 at 20:33 +0200, Rémi Cardona wrote:
> Chris Gianelloni wrote:
> > It's simple.  You mask expat-2.0.0 on all the current profiles, we mark
> > it stable in the snapshot and don't have it masked in the 2007.1
> > profile.  When we release (actually right before), we mark the package
> > stable in the tree.  We document the expat upgrade as part of the
> > profile upgrade guide, and we're done.  Users using a <=2007.0 profile
> > never see the upgrade.  New users use the new expat.  Users changing to
> > the 2007.1 profile run revdep-rebuild.
> 
> +1
> 
> Now, how can we do this? Could we start changing the profiles right now?

Considering we already have a 2.0.0 ebuild, we do the following:

- Mask >=2.0.0-r9 (this allows for security bumps, if necessary, number
can be adjusted)
- Copy 2.0.0 to 2.0.0-r9
- When we make a new 2007.1 profile, don't mask >=2.0.0-r9
- Stable 2.0.0-r9 in the 2007.1 snapshot and mark it stable in the tree
with the release
- ???
- Profit!

> (I guess people on ~arch will need to unmask it to not downgrade).

Well, with what I have said, there's room for version bumps, if
required.  It also means ~arch people don't have to do anything.  There
won't be any downgrade and we simply never mark anything below 2.0.0-r9
stable to keep stable users safe.

> Should this be brought to the next council meeting?

Is that really necessary?  What can the Council do that we cannot agree
upon here as civil adults?  I think we can agree to do this ourselves.
I can definitely agree to it from a Release Engineering standpoint.  It
would work quite well and is beneficial to our users.

> Chris, I could write a small paragraph for whatever GWN explaining what
> stable and unstable users will have to do if you want.

Sure.  However, if we did follow my draft plan above, there would be no
need.  Users running ~arch have probably hit this already by now, so I
don't think we would be informing too many people.  That being said, it
would make a cool article.  Even if just to show that, yes, we really do
care for our users and think about ways to reduce the impact on their
systems.

-- 
Chris Gianelloni
Release Engineering Strategic Lead
Alpha/AMD64/x86 Architecture Teams
Games Developer/Council Member/Foundation Trustee
Gentoo Foundation

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2007-05-17 21:10 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-15 11:30 [gentoo-dev] stabilizing expat 2.0.0 Caleb Tennis
2007-05-15 11:40 ` Mart Raudsepp
2007-05-15 11:47   ` Caleb Tennis
2007-05-15 12:12     ` Mart Raudsepp
2007-05-15 13:41       ` Caleb Tennis
2007-05-15 14:12         ` Caleb Tennis
2007-05-15 14:26           ` Jakub Moc
2007-05-15 16:13             ` Caleb Tennis
2007-05-15 15:14       ` Carsten Lohrke
2007-05-15 15:29         ` [gentoo-dev] " Christian Faulhammer
2007-05-16 15:09           ` Wulf C. Krueger
2007-05-18 21:34             ` Christian Faulhammer
2007-05-18 21:46               ` Raúl Porcel
2007-05-16 15:39         ` [gentoo-dev] " Raúl Porcel
2007-05-16 16:12           ` Carsten Lohrke
2007-05-16 22:05         ` [gentoo-dev] " Steve Long
2007-05-16 22:15           ` Jakub Moc
2007-05-18 21:33           ` Christian Faulhammer
2007-05-19 18:51             ` Daniel Gryniewicz
2007-05-15 11:41 ` [gentoo-dev] " Ciaran McCreesh
2007-05-15 11:45   ` Caleb Tennis
2007-05-15 12:21   ` Mike Frysinger
2007-05-15 12:22 ` Mike Frysinger
2007-05-15 12:27   ` Ciaran McCreesh
2007-05-15 12:52     ` Mike Frysinger
2007-05-15 13:27       ` Ciaran McCreesh
2007-05-15 14:02         ` Petteri Räty
2007-05-15 14:07           ` Ciaran McCreesh
2007-05-15 14:15     ` Carsten Lohrke
     [not found]   ` <4649AA12.6040107@gentoo.org>
2007-05-15 13:38     ` Caleb Tennis
2007-05-15 14:11       ` Carsten Lohrke
2007-05-15 13:58     ` [gentoo-dev] " Mike Frysinger
2007-05-15 17:22 ` Duncan
2007-05-15 18:08   ` Rémi Cardona
2007-05-15 21:19     ` Markus Ullmann
2007-05-16 17:24     ` Chris Gianelloni
2007-05-16 17:31       ` Petteri Räty
2007-05-16 17:48         ` Caleb Tennis
2007-05-17  7:57           ` Duncan
2007-05-17  9:32             ` Rumen Yotov
2007-05-17 10:21               ` Rémi Cardona
2007-05-17 17:59             ` Chris Gianelloni
2007-05-17 21:32               ` Duncan
2007-05-17 18:05           ` Chris Gianelloni
2007-05-17 18:33             ` Rémi Cardona
2007-05-17 18:38               ` Vlastimil Babka
2007-05-17 21:05                 ` Chris Gianelloni
2007-05-17 21:05               ` Chris Gianelloni [this message]
2007-05-18  1:17                 ` [gentoo-dev] " Steve Long
2007-05-16 17:49       ` [gentoo-dev] " Rémi Cardona

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1179435917.25168.10.camel@workbox.quova.com \
    --to=wolf31o2@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox