Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <koen@dominion.kabel.utwente.nl>
To: openembedded-devel@openembedded.org
Cc: angstrom-distro-devel@linuxtogo.org
Subject: Re: [Angstrom-devel] [RFC] Changing stable branch commit policy
Date: Sat, 29 Mar 2008 11:48:37 +0100	[thread overview]
Message-ID: <fsl6q5$gt0$1@ger.gmane.org> (raw)
In-Reply-To: <c384c5ea0803281342j3f836b8cibbf1b9030a5d2859@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Leon Woestenberg schreef:
| Hello all,
|
|> Do you want to write a short blurb on this we can stick on the oe and
angstrom websites? regards, Koen
|
| Sure, a first shot at that (and sorry for cross-posting, but this
| really is OE related :-)
|
| ---
| The OpenEmbedded project has started to maintain a stable branch, next
| to its development branch, on March 28th 2007. Besides
| "org.openembedded.dev" there now is the "org.openembedded.stable"
| branch.
|
| The plumbing work on the development branch (long-term improvements
| such as packaged staging, creating stand-alone SDK toolchains and a
| new package manager) colides with the goal of offering a stable base
| for OpenEmbedded-derived distributions. Some projects, most notably
| the Angstrom distribution, already maintained a stable branch for this
| reason.
|
| The effort of maintaining a stable branch is now centralized back into
| the OpenEmbedded project. The main goal of the stable branch is to
| provide a branch that progresses in time with a minimum of disruptive
| changes, especially to the framework, which include classes,
| configuration namespace, package management, and tooling such as the
| bitbake tool. Changes to the stable branch are selected and reviewed
| according to an agreed upon policy before being committed to the
| stable branch. This will require extra effort from the OpenEmbedded
| developer community.
|
| The stable branch is not intended to keep up with the pace of
| development on the development branch. Planned is to create new stable
| branches every year; the next stable branch is scheduled to branch of
| the development tree during 2008.12. Old stable branches will go in
| unmaintained mode 3 months after a new stable branch is created; the
| current stable will retire 2009.2.
|
| OpenEmbedded projects and distributions now have the choice of at
| least a .dev and .stable branch and the OpenEmbedded developers can
| keep on plumbing.
| ---

The mailinglist:

http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-stablebranch

And viewmtn:

http://amethyst.openembedded.net/oe/viewmtn/viewmtn.py/branch/changes/org.openembedded.stable

The commit policy (currently under RFC at the above mailinstlist):

http://linuxtogo.org/gowiki/Angstrom/Backport_from_dev_to_stable

regards,

Koen



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFH7h6FMkyGM64RGpERAslYAJ9m9k3kwSiTfbPN8jLFxfIx5HAhugCfZfQx
/eUCqwLdgYJv3pQdkYBX/S8=
=FVoH
-----END PGP SIGNATURE-----




  parent reply	other threads:[~2008-03-29 10:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <022890FE-5E72-489F-B64C-03593101E508@student.utwente.nl>
     [not found] ` <47E83808.5060501@balister.org>
     [not found]   ` <c384c5ea0803271304i4739ea3bpee3ace5854384f4c@mail.gmail.com>
     [not found]     ` <fsgvoq$545$1@ger.gmane.org>
     [not found]       ` <c384c5ea0803271622i59f5e3bai2a9606e749a0611b@mail.gmail.com>
     [not found]         ` <fsjbi5$hak$1@ger.gmane.org>
2008-03-28 20:42           ` [Angstrom-devel] [RFC] Changing stable branch commit policy Leon Woestenberg
2008-03-29  2:03             ` Holger Freyther
2008-03-29 10:48             ` Koen Kooi [this message]
2008-03-29 12:13               ` Leon Woestenberg

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='fsl6q5$gt0$1@ger.gmane.org' \
    --to=koen@dominion.kabel.utwente.nl \
    --cc=angstrom-distro-devel@linuxtogo.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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