openembedded-devel.lists.openembedded.org archive mirror
 help / color / mirror / Atom feed
From: Phil Blundell <philb@gnu.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Preparing for release - Freeze on master
Date: Thu, 18 Nov 2010 10:08:23 +0000	[thread overview]
Message-ID: <1290074903.3183.202.camel@mill.internal.reciva.com> (raw)
In-Reply-To: <AANLkTimdqZ1hdZNPN70LXd1WuJSn4pU2y=2C5tZs0-LT@mail.gmail.com>

On Wed, 2010-11-17 at 11:26 -0800, Khem Raj wrote:
> Should we create a release branch before we release and solidify that ? 

Yes, please do that.  We discussed this issue at yesterday's TSC meeting
(full minutes to follow shortly) and the consensus was that trying to
enforce a complete freeze on master at short notice is not going to be
practical.

Obviously the exact process you use is up to you, but I would suggest
something along the lines of:

1. make a stabilisation branch from some semi-arbitrary point, maybe one
of the existing weekly test versions.

2. do testing on this branch.

3. cherry-pick and/or revert changesets on the branch as
necessary/desired.

4. iterate steps 2/3 until you are happy with the quality or the
deadline is reached.

5. tag the release from the current head of that branch.

p.





  reply	other threads:[~2010-11-18 10:09 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-16 18:20 Preparing for release - Freeze on master Khem Raj
2010-11-16 22:39 ` Paul Menzel
2010-11-16 22:46   ` Khem Raj
2010-11-16 22:52     ` Frans Meulenbroeks
2010-11-16 23:00       ` Khem Raj
2010-11-17  7:16         ` Frans Meulenbroeks
2010-11-17  9:12 ` Koen Kooi
2010-11-17  9:56   ` Graeme Gregory
2010-11-17 10:25     ` Koen Kooi
2010-11-17 19:26       ` Khem Raj
2010-11-18 10:08         ` Phil Blundell [this message]
2010-11-18 11:01           ` Graham Gower
2010-11-18 11:31             ` Phil Blundell
2010-11-18 17:18               ` Philip Balister
2010-11-18 11:09           ` Frans Meulenbroeks
2010-11-18 14:07             ` Chris Larson
2010-11-18 16:32           ` Khem Raj
2010-11-19 10:29           ` Koen Kooi
2010-11-17 19:20     ` Khem Raj
2010-11-17 19:15   ` Khem Raj

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=1290074903.3183.202.camel@mill.internal.reciva.com \
    --to=philb@gnu.org \
    --cc=openembedded-devel@lists.openembedded.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;
as well as URLs for NNTP newsgroup(s).