From: Chris Larson <clarson@kergoth.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Preparing for release - Freeze on master
Date: Thu, 18 Nov 2010 07:07:48 -0700 [thread overview]
Message-ID: <AANLkTi=7ixLgaKr5LKxsfgtJyCPaaxBrWkmOih9GHnq3@mail.gmail.com> (raw)
In-Reply-To: <AANLkTin4uoJzqtd0G5Z+gS_Y+-kxpgojKm92jkJ8jnLy@mail.gmail.com>
On Thu, Nov 18, 2010 at 4:09 AM, Frans Meulenbroeks <
fransmeulenbroeks@gmail.com> wrote:
> 2010/11/18 Phil Blundell <philb@gnu.org>:
>
> >
> > 1. make a stabilisation branch from some semi-arbitrary point, maybe one
> > of the existing weekly test versions.
>
> Seems fine with me. I suggest to start with the testing branch that is
> to be made today.
> that avoids having to pick the changes that are done for the release
> on the master branch last week.
>
Just a reminder that this stabilization branch should only exist from this
semi-arbitrary point to the point when the release is tagged -- the branch
should then be removed, to ensure no one thinks it is a long term
maintenance branch, which it is not.
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
next prev parent reply other threads:[~2010-11-18 14: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
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 [this message]
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='AANLkTi=7ixLgaKr5LKxsfgtJyCPaaxBrWkmOih9GHnq3@mail.gmail.com' \
--to=clarson@kergoth.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.