[Angstrom-devel] [RFC] Changing stable branch commit policy

2008-03-24 Thread Koen Kooi
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, This weekend I worked on backporting the autotools.bbclass and base.bbclass changes that fix .la files, so the autobuilder (which uses rm_work) can finally build e-wm. After inspecting the changes and some serious time with meld I have a bac

Re: [Angstrom-devel] [RFC] Changing stable branch commit policy

2008-03-24 Thread Philip Balister
Koen Kooi wrote: If we drop the bookkeeping part, getting things into the stable tree will be much easier: * send explanation and diff to angstrom-distro-devel * 2 developers sign off on it * apply diff * copy-paste explanation into NEWS or Changelog This makes a faster turnaround possible, s

Re: [Angstrom-devel] [RFC] Changing stable branch commit policy

2008-03-24 Thread Junqian Gordon Xu
On 03/24/2008 05:41 PM, Koen Kooi wrote: > This weekend I worked on backporting the autotools.bbclass and > base.bbclass changes that fix .la files, so the autobuilder (which > uses rm_work) can finally build e-wm. After inspecting the changes and > some serious time with meld I have a backpo

Re: [Angstrom-devel] [RFC] Changing stable branch commit policy

2008-03-24 Thread Hans Henry von Tresckow
On Mon, Mar 24, 2008 at 3:41 PM, Koen Kooi <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi, > > This weekend I worked on backporting the autotools.bbclass and > base.bbclass changes that fix .la files, so the autobuilder (which > uses rm_work) can finally build

Re: [Angstrom-devel] [RFC] Changing stable branch commit policy

2008-03-25 Thread Koen Kooi
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Junqian Gordon Xu schreef: | | The bigger question is what's the fate of the current stable branch. How | long are we going to keep it maintained? That's up to angstrom developers to decide. My gut feeling is that the 2008 release is at least 6 month

Re: [Angstrom-devel] [RFC] Changing stable branch commit policy

2008-03-27 Thread Leon Woestenberg
Hello all, On Tue, Mar 25, 2008 at 12:23 AM, Philip Balister <[EMAIL PROTECTED]> wrote: > Koen Kooi wrote: > > If we drop the bookkeeping part, getting things into the stable tree > > will be much easier: > > ... > > objections, additions? > > +1 > > At some point in time, a stable and devel

Re: [Angstrom-devel] [RFC] Changing stable branch commit policy

2008-03-27 Thread Koen Kooi
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Leon Woestenberg schreef: | Hello all, | | On Tue, Mar 25, 2008 at 12:23 AM, Philip Balister <[EMAIL PROTECTED]> wrote: |> Koen Kooi wrote: |> > If we drop the bookkeeping part, getting things into the stable tree |> > will be much easier: |> > ...

Re: [Angstrom-devel] [RFC] Changing stable branch commit policy

2008-03-27 Thread Leon Woestenberg
Hello Koen, On Thu, Mar 27, 2008 at 9:23 PM, Koen Kooi <[EMAIL PROTECTED]> wrote: > | If not done yet, we have to decide to go for one of two approaches. > | (1) .stable tracks .dev, but lags. Takes lots of efforts. > | (2) .stable diverges from .dev, not keeping up at some point. The > | "fis

Re: [Angstrom-devel] [RFC] Changing stable branch commit policy

2008-03-28 Thread Koen Kooi
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Leon Woestenberg schreef: | Hello Koen, | | On Thu, Mar 27, 2008 at 9:23 PM, Koen Kooi | <[EMAIL PROTECTED]> wrote: |> | If not done yet, we have to decide to go for one of two approaches. |> | (1) .stable tracks .dev, but lags. Takes lots of efforts

Re: [Angstrom-devel] [RFC] Changing stable branch commit policy

2008-03-28 Thread Leon Woestenberg
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 deve

Re: [Angstrom-devel] [RFC] Changing stable branch commit policy

2008-03-29 Thread Stelios Koroneos
> > | I am very much in favor of keeping the tooling/framework/classes > | largely feature-frozen within a stable branch, and > selectively upgrade > | packages. > > That is my idea as well, I did backport the native.bbclass > change since it fixed rm_work, which is very important since > th