All of lore.kernel.org
 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 11:31:14 +0000	[thread overview]
Message-ID: <1290079874.3183.222.camel@mill.internal.reciva.com> (raw)
In-Reply-To: <AANLkTimnEoW_9i8T65WTsQsYXc2E2gcx+015o13cVsKF@mail.gmail.com>

On Thu, 2010-11-18 at 21:31 +1030, Graham Gower wrote:
> So, why not just branch it already and apply the same commit policy as 
> the existing stable branch.

Essentially because nobody has yet volunteered to do the ongoing
maintenance work that would be involved in having a long-lived stable
branch.  And, if OE is going to have releases off master on a fairly
frequent schedule (I think the proposal is four releases per year or
thereabouts) then the requirement for such a branch is somewhat
diminished.

If you're interested in doing the work to maintain a new stable branch
along the same lines as stable/2009, and you can commit the time that is
required to make it work, then you are certainly very welcome to do so.
You don't need any particular permission to do this: you can (subject to
the Branching Policy) create a new branch at any time.

p.





  reply	other threads:[~2010-11-18 11:32 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
2010-11-18 11:01           ` Graham Gower
2010-11-18 11:31             ` Phil Blundell [this message]
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=1290079874.3183.222.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 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.