Openembedded Devel Discussions
 help / color / mirror / Atom feed
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 21:22:53 +0200	[thread overview]
Message-ID: <20100720192253.GN1512@excalibur.local> (raw)
In-Reply-To: <AANLkTikYdD7jzsJBNEK0MedOmM_jHIEcdCfE0APMSOqt@mail.gmail.com>

Hello.

On Tue, 2010-07-20 at 21:07, Esben Haabendal wrote:
> On Tue, Jul 20, 2010 at 7:34 PM, Stefan Schmidt
> <stefan@datenfreihafen.org> wrote:
> > On Tue, 2010-07-20 at 18:56, Koen Kooi wrote:
> >> 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.
> >
> > Sure, that is no surprise. :)
> 
> It might be surprising to some, but some of those not actively
> supporting the "stable" branch might choose not to do so because the
> chosen stable process does not fit their needs.
> Most likely, all people contributing to stable is mostly happy with
> how it is handled.

People who add a "me, too" for a new stable branch seem to think that they fit
their needs.

What does not fit your needs with the current stable handling?

I would like to have a more continous flow of changes from dev over some testing
branch to stable. As indicated in my initial mail. That would people working on
this idea and keeping it alive though. Given that no one seemed to be interested
but man seem to be interested to get a new stable/2010 branch the same way we
had for 2009 it seems the most practical way to get one at all, no?

Other models will only work if enough support from the active contributors is
available. Without this even the best idea might die.

regards
Stefan Schmidt



  reply	other threads:[~2010-07-20 19:23 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
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 [this message]
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=20100720192253.GN1512@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