From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] New stable branch (and maybe a new process?)
Date: Tue, 20 Jul 2010 06:01:26 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1007200556270.8124@lynx> (raw)
In-Reply-To: <4C45619F.1060201@2net.co.uk>
On Tue, 20 Jul 2010, Chris Simmonds wrote:
> On 20/07/10 08:01, Stefan Schmidt wrote:
> > Hello.
> >
> > On Fri, 2010-07-09 at 22:40, Stefan Schmidt wrote:
> > >
> > > I want to gather some feedback what people are feeling about a new stable
> > > branch. It feels like the right time to do it soon. We have so many big
> > > changes
> > > in that are not likely to get into stable/2009 like:
> >
> > > From the silence on this topic I gather that the interest to create a new
> > > branch
> > or change the process is quite low.
> >
>
> I would like to vote for a 2010 stable branch. There is a lot of
> good stuff in the dev branch that I would like to use in live
> projects.
i second that, with the proviso that the primary focus for that
new stable branch be on resolving any unbuildable packages for major
distros. as i've whined about before, there always seems to be a
package or two from the dev branch that doesn't build on my standard
64-bit ubuntu system (last time i checked, it was abiword). i just
did a git pull on the dev branch and am checking again to see what
fails.
not to belabour the point, but if a new branch is created and tagged
as "stable," it should build for anyone using any of the common
distros.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Top-notch, inexpensive online Linux/OSS/kernel courses
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next prev parent reply other threads:[~2010-07-20 10:03 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
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 [this message]
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=alpine.DEB.2.00.1007200556270.8124@lynx \
--to=rpjday@crashcourse.ca \
--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