Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Junqian Gordon Xu <xjqian@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: openembedded-devel@openembedded.org
Subject: Re: Autobuilder bugs versus stable branch being updated
Date: Tue, 17 Feb 2009 17:21:28 -0600	[thread overview]
Message-ID: <499B4678.4030202@gmail.com> (raw)
In-Reply-To: <20090217215529.GJ11815@smtp.west.cox.net>

On 02/17/2009 03:55 PM, Tom Rini wrote:
> On Tue, Feb 17, 2009 at 08:54:46PM +0100, Bernhard Guillon wrote:
>> Rolf Leggewie wrote:
>>> Philip,
>>>
>>> thank you for your comment.
>>>
>>> Philip Balister wrote:
>>>> I think it is a but of stretch to close old autobuilder bugs with the 
>>>> comment the stable branch will not be updated.
>>> That should not be the case (unless of course they were both of type  
>>> .stable and -autobuild).
>>>
>> We should create a new stable branch. The old one drifted too much away  
>> from .dev which makes it hard to backport things from .dev to stable.
> 
> The problem really is a policy one.  The old stable was "angstrom
> snapped for 2007 here".  That's one way to do a stable branch, but not
> what everyone thinks when they read "stable".  How much would it hurt to
> have OE actually do releases, rather than to be, in kernel terms, mostly
> like Andrew's tree (once stuff seems to work for some people, pull it
> in, see what breaks)?

+1 for releases instead of snap short, which was proven not working for 
the users.

> 
> And of course, who would volunteer to actually try and maintain such
> things and get everyone using the various branches that would have to
> entail, correctly?
> 

I can maintain the user space stuffs and communicate/bug core members 
for stuff that I do not understand. In terms of machines, I will keep an 
eye on tosa and spitz. I've been away for a while since the git 
conversion (now half-way through the git manual), but I always try to 
keep up with the mailing lists.

Regards
Gordon



  reply	other threads:[~2009-02-17 23:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-17 15:33 Autobuilder bugs versus stable branch being updated Philip Balister
2009-02-17 17:16 ` Rolf Leggewie
2009-02-17 19:54   ` Bernhard Guillon
2009-02-17 21:42     ` Koen Kooi
2009-02-17 22:33       ` Bernhard Guillon
2009-02-17 21:55     ` Tom Rini
2009-02-17 23:21       ` Junqian Gordon Xu [this message]
2009-02-18 16:11         ` Sledz, Steffen

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=499B4678.4030202@gmail.com \
    --to=xjqian@gmail.com \
    --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