From: Stefan Schmidt <stefan@datenfreihafen.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] New stable branch (and maybe a new process?)
Date: Tue, 20 Jul 2010 15:32:51 +0200 [thread overview]
Message-ID: <20100720133251.GK1512@excalibur.local> (raw)
In-Reply-To: <4C45A062.6080606@balister.org>
Hello.
On Tue, 2010-07-20 at 09:10, Philip Balister wrote:
> On 07/20/2010 04:40 AM, Stefan Schmidt wrote:
> >On Tue, 2010-07-20 at 10:09, Koen Kooi wrote:
> >
> >>The biggest problem is the .dev is halfway into big changes, e.g.
> >>halfway into new-style staging,
> >
> >Agreed. While I think we are more then halfway through with this. Recipes are
> >left but most of the active maintained are already done. NO numbers but my
> >feeling here.
> >
> >>halfway into packaged-staging rework, halfway into nativesdk, etc.
> >
> >These both are ongoing for quite some time already. I have to admit that I lost
> >track where they stand and what is still outstanding.
> >
> >So your suggestion is to wait until all three are done?
>
> We should identify the work in progress in dev and decide which ones
> we should finish before creating a new staging. There is no sense
> making a new stable branch and then creating a major diversion from
> dev that will make maintaining both in parallel for as long as
> possible difficult.
Does my mail read as if I wanted to rush this in? If yes, that was not my
intend.
I'm interested in new stable branch. I had a moment where I hoped it would be
ready in time for our upcoming BUG2.0 release, but this moment is over already.
Neverless I want to see it happened and it should not be rushed in.
The question was completely honest. Is the idea to wait until all three are
finished (for every recipe in tree)?
For the new staging I could imagine that we could get close. Of course minus all
the recipes in tree nobody maintains. A problem we always have and which does
not go away in a stable snapshot.
For packaged staging it may come true as well, but the nativesdk part I see
mostly arguing back and forth. So if the people listed as stable maintainers
come to the conclusion that we should wait for all three that is fine with me.
Maybe a roadmap what you guys want to have ready before branching of would help
others then.
regards
Stefan Schmidt
next prev parent reply other threads:[~2010-07-20 13:33 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-09 20:40 [RFC] New stable branch (and maybe a new process?) Stefan Schmidt
2010-07-10 6:51 ` 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 [this message]
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=20100720133251.GK1512@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