From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: 2011.03 release testing, starts soon!
Date: Wed, 09 Feb 2011 07:47:44 -0700 [thread overview]
Message-ID: <4D52A910.4060407@mentor.com> (raw)
In-Reply-To: <09D9BE2AC4AA764DABAA8C91E48D819E011A79A329@DEMCHP99E35MSX.ww902.siemens.net>
On 02/09/2011 02:25 AM, Aeschbacher, Fabrice wrote:
> Hi all,
>
> There are two things which could be useful (IMO) for OE users:
>
> 1. a small README file (or wiki page) just highlighting the main
> changes since last release (2010.12), e.g. something like
> "Prominent features (the cool stuff)" on http://kernelnewbies.org/LinuxChanges
> This would help us OE users to decice whether it is worth rebasing on the latest
> release now, or if it can wait
Great idea! I've added a place-holder to the wiki page for the release.
> 2. Do not delete the release branch after 2011.03 will be released (just like
> it was done for 2010.12), but let it live and allow developpers committing
> bug-fixes (backporting choosen things?) reported back by OE users (some would
> would be happy to contribute this way)
My _hope_ is to not have to make a branch to take from, but we shall
see. Beyond that, I see the discussion about keeping something that's
not just top of tree alive as an important but only related discussion.
Starting from the release tag is probably the best bet, should
something want to happen in that direction.
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2011-02-09 14:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-08 19:41 2011.03 release testing, starts soon! Tom Rini
2011-02-09 9:25 ` Aeschbacher, Fabrice
2011-02-09 9:56 ` Stefan Schmidt
2011-02-09 10:18 ` Koen Kooi
2011-02-09 10:42 ` Stefan Schmidt
2011-02-09 11:20 ` Koen Kooi
2011-02-09 20:30 ` Khem Raj
2011-02-10 8:31 ` Stefan Schmidt
2011-02-09 14:47 ` Tom Rini [this message]
2011-02-10 9:42 ` Aeschbacher, Fabrice
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=4D52A910.4060407@mentor.com \
--to=tom_rini@mentor.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox