Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Stefan Schmidt <stefan@datenfreihafen.org>
To: openembedded-devel@lists.openembedded.org
Subject: [RFC] New stable branch (and maybe a new process?)
Date: Fri, 9 Jul 2010 22:40:55 +0200	[thread overview]
Message-ID: <20100709204055.GA12163@excalibur.local> (raw)

Hello.

I want to gather some feedback what people are feeling about a new stable
branch. It feels like the right time to do it soon. We have so many big changes
in that are not likely to get into stable/2009 like:

- New staging
- BBCLASSEXTEND
- Checksums in recipes
- Faster BitBake
- Enhanced java support with openjdk/icedtea
- And many I forgot...

With the latest fixes for the file:// problem the build feels stable at last for
me. I have not been involved with the latest stable branch so this is really
only a RFC from my side. Please let me know if you see big issues for such a
move.

Open questions:
---------------
- Do we feel comfortable with doing a new branch now?
- What version of bitbake we would like to have for this?
- What boards/images/distros will be supported in stable/2010?

I my be biased here regarding my work for BugLabs, but I feel me diverged that
much from stable/2009 that it gets problematic to get changes in and syncing
them with .dev. As well the overall build experience on .dev is pretty good the
last weeks. The file:// problems aside.

Another idea we just discussed on IRC was to have a model somehow related to
what debian is using. An ongoing flow of patches from .dev to a testing branch.
Perhaps automated with buildbot to move into testing when some certain builds
have passed with this commit. And also an _ongoing_ stream well tested patches
from testing into stable which eventually makes a time-based release every X
months form this ond move on.

That all needs to be filled with more details, but it could be a start. Let me
know what you think.

regards
Stefan Schmidt



             reply	other threads:[~2010-07-09 20:45 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-09 20:40 Stefan Schmidt [this message]
2010-07-10  6:51 ` [RFC] New stable branch (and maybe a new process?) Frans Meulenbroeks
2010-07-12  6:50   ` Stefan Schmidt
2010-07-13 18:36 ` Stefan Schmidt
2010-07-20  7:01 ` Stefan Schmidt
2010-07-20  8:09   ` Koen Kooi
2010-07-20  8:40     ` Stefan Schmidt
2010-07-20 11:20       ` Detlef Vollmann
2010-07-20 13:10       ` Philip Balister
2010-07-20 13:32         ` Stefan Schmidt
2010-07-20 16:56       ` Koen Kooi
2010-07-20 17:34         ` Stefan Schmidt
2010-07-20 18:42           ` Koen Kooi
2010-07-20 19:04             ` Stefan Schmidt
2010-07-20 22:09               ` Richard Purdie
2010-07-20 19:16             ` Tom Rini
2010-07-20 20:58               ` Koen Kooi
2010-07-20 23:07                 ` Tom Rini
2010-07-20 23:24                   ` Tom Rini
2010-07-20 21:31             ` Frans Meulenbroeks
2010-07-20 19:07           ` Esben Haabendal
2010-07-20 19:22             ` Stefan Schmidt
2010-07-21  5:58               ` Esben Haabendal
2010-07-21  7:13                 ` Frans Meulenbroeks
2010-07-22 18:40                   ` Khem Raj
2010-07-20  8:43   ` Chris Simmonds
2010-07-20 10:01     ` Robert P. J. Day
2010-07-20 10:12     ` Jaap de Jong
2010-07-20 11:06       ` Christophe Aeschlimann

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=20100709204055.GA12163@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox