All of lore.kernel.org
 help / color / mirror / Atom feed
From: Graeme Gregory <dp@xora.org.uk>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Preparing for release - Freeze on master
Date: Wed, 17 Nov 2010 09:56:46 +0000	[thread overview]
Message-ID: <4CE3A6DE.2070203@xora.org.uk> (raw)
In-Reply-To: <ic06a8$uft$1@dough.gmane.org>

On 17/11/2010 09:12, Koen Kooi wrote:
> On 16-11-10 19:20, Khem Raj wrote:
> > Hello All,
>
> > In order to get to the 2010.12 release, I would like to request to
> > stop pushing any changes to master until release. Please keep your
> > changes in you local tree ready for when the window
> > opens again after the release.
>
> At OEDEM we agreed that the release would pick a tested branch tag to
> avoid such a draconic freeze.
>
I must say I am puzzled why the freeze when git supports branches. In
the past we have just picked a point branched then cherry picked
anything interesting that went into org.openemedded.dev until release date.

Graeme




  reply	other threads:[~2010-11-17  9:57 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 [this message]
2010-11-17 10:25     ` Koen Kooi
2010-11-17 19:26       ` Khem Raj
2010-11-18 10:08         ` Phil Blundell
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=4CE3A6DE.2070203@xora.org.uk \
    --to=dp@xora.org.uk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.