All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] New stable branch (and maybe a new process?)
Date: Tue, 20 Jul 2010 18:56:06 +0200	[thread overview]
Message-ID: <i24kf7$3d3$1@dough.gmane.org> (raw)
In-Reply-To: <20100720084026.GI1512@excalibur.local>

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

On 20-07-10 10:40, Stefan Schmidt wrote:
> Hello.
> 
> On Tue, 2010-07-20 at 10:09, Koen Kooi wrote:
>> On 20-07-10 09:01, Stefan Schmidt wrote:
>>>
>>> From the silence on this topic I gather that the interest to create a new branch
>>> or change the process is quite low.
>>
>> I have an interest in a new stable branch, but no interest in changing
>> the process.
> 
> Fair enough. Lets handle the issues seperately for now.
> 
>> 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?

'Wait' is maybe the wrong word. I would try to do a call to arms to get
more people interested into getting this done. I had hoped that the TSC
would be more vocal about this, but we must do with the cards dealt.

And of course the number of people screaming for a stable branch is an
order of magnitude larger than the number of people that end up actually
supporting it.

regards,

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

iD8DBQFMRdUmMkyGM64RGpERAmlcAJ0TbmzdYV6Z8p+FdtCP1jwXWOdIowCfbEJ9
8Zyd7nsYgEZZfj2daMq+EdI=
=gEzx
-----END PGP SIGNATURE-----




  parent reply	other threads:[~2010-07-20 16:56 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
2010-07-20 16:56       ` Koen Kooi [this message]
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='i24kf7$3d3$1@dough.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --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.