All of lore.kernel.org
 help / color / mirror / Atom feed
From: Graham Gower <graham.gower@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Preparing for release - Freeze on master
Date: Thu, 18 Nov 2010 21:31:32 +1030	[thread overview]
Message-ID: <AANLkTimnEoW_9i8T65WTsQsYXc2E2gcx+015o13cVsKF@mail.gmail.com> (raw)
In-Reply-To: <1290074903.3183.202.camel@mill.internal.reciva.com>

 Everyone is going to want to apply fixes to the release, so it makes
sense to have this as a new stable branch.

OE is in a relatively stable state right now with no major changes
causing large fallout recently. So, why not just branch it already and
apply the same commit policy as the existing stable branch.

More importantly are the logistics of handling what fixes go onto the
both branches or only the dev branch. Since the current stable branch
has been stale since I became involved in OE, I don't really know how
this works but I am very interested in submitting fixes for a stable
branch over the next few months.

-Graham



  reply	other threads:[~2010-11-18 11:02 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 [this message]
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=AANLkTimnEoW_9i8T65WTsQsYXc2E2gcx+015o13cVsKF@mail.gmail.com \
    --to=graham.gower@gmail.com \
    --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.