Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: OpenEmbedded Release 2010.12 --- needs your help!
Date: Thu, 04 Nov 2010 18:47:52 -0400	[thread overview]
Message-ID: <20101104224752.GH28852@denix.org> (raw)
In-Reply-To: <4CD3349D.6060904@eukrea.com>

On Thu, Nov 04, 2010 at 11:33:01PM +0100, Eric B?nard wrote:
> Hi,
>
> Le 04/11/2010 23:06, Denys Dmytriyenko a ?crit :
>> On Thu, Nov 04, 2010 at 09:04:43PM +0100, Leon Woestenberg wrote:
>>> Hello all,
>>>
>>> at OEDEM we discussed the need for OpenEmbedded releases.
>>>
>>> - OpenEmbedded releases are planned in certain months, so that we can
>>> plan stabilization efforts in the future.
>>> - Each release is a point release in time.
>>> - A release is a candidate branch point for a stable branch (which can
>>> be maintained by those who use it).
>>> - The next release is planned 2010.12, more specifically December 1st.
>>> That's only four weeks from now.
>>> - The 2010.12 release is hand-picked from a recent testing branch.
>>
>> - OpenEmbedded releases are planned to be time based and happen every 3 
>> month
>> (quarterly), starting with the first one on December 1st.
>>
> - what about a "no major change" freeze period for 2-3 weeks before each 
> release to have a enough time to stabilize a little bit the beast ?

I thought Leon kind of mentioned it in the first bullet point above, but 
probably not very clear. And yes, we definitely need a 2-3 weeks "feature 
freeze" period for stabilization. Thanks for pointing it out.

>>> Now that our testing team has the process in place to gather test
>>> results, please consider to build your
>>> favorite set of distro/machine targets using tinderbox, and report your 
>>> results.
>>>
>>> One requirement is to use bitbake 1.10, as the minimal requirement
>>> will soon be 1.10 for the OpenEmbedded metadata.

-- 
Denys



  parent reply	other threads:[~2010-11-04 22:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-04 20:04 OpenEmbedded Release 2010.12 --- needs your help! Leon Woestenberg
2010-11-04 20:31 ` Khem Raj
2010-11-04 22:06 ` Denys Dmytriyenko
2010-11-04 22:33   ` Eric Bénard
2010-11-04 22:47     ` Graham Gower
2010-11-04 22:47     ` Denys Dmytriyenko [this message]
2010-11-05  6:52       ` Martin Jansa
2010-11-05  7:27         ` Stefan Schmidt
2010-11-05  9:22         ` Eric Bénard
2010-11-05  9:49           ` Martin Jansa
2010-11-05 10:03             ` Eric Bénard
2010-11-05 13:32               ` Paul Menzel
2010-11-05 13:52                 ` Martin Jansa
2010-11-04 22:14 ` Denys Dmytriyenko
2010-11-05  0:23   ` Richard Purdie
2010-11-05  9:08 ` Marco Cavallini

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=20101104224752.GH28852@denix.org \
    --to=denis@denix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox