All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Schmidt <stefan@datenfreihafen.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: OpenEmbedded Release 2010.12 --- needs your help!
Date: Fri, 5 Nov 2010 08:27:17 +0100	[thread overview]
Message-ID: <20101105072717.GC3702@excalibur.local> (raw)
In-Reply-To: <20101105065240.GI3440@jama>

Hello

On Fri, 2010-11-05 at 07:52, Martin Jansa wrote:
> On Thu, Nov 04, 2010 at 06:47:52PM -0400, Denys Dmytriyenko wrote:
> > 
> > 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.
> 
> what about branching future release those 2-3 weeks ago and keep master
> for active development?
> 
> I know it could lower number of people using this future release branch
> during testing period before release, but still seems better then
> pushing 3 weeks of commits from my local branch as soon as release is
> branched and master open for new recipes again.

I don't think this would be a good idea. Part of the problem that we haven't
been able to do releases in the past was a development style of "dumping"
everything into master all the time. If we are able to adapt a more release
driven workflow with branches for upcoming features and a period of
stabilization in the master branch I feel that we are better prepared to bring
out releases for OE.

A lot of changes that are made like new recipes, depends fixes, packaging fixes,
etc are small enough to slip in every time. The stuff we should avoid in the
last weeks are changes touching classes, toolchain changes and other core
things.

regards
Stefan Schmidt



  reply	other threads:[~2010-11-05  7:28 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
2010-11-05  6:52       ` Martin Jansa
2010-11-05  7:27         ` Stefan Schmidt [this message]
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=20101105072717.GC3702@excalibur.local \
    --to=stefan@datenfreihafen.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.