From: Martyn Welch <martyn.welch@ge.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: What to do about the poor bitbake Quality Control?
Date: Wed, 18 Aug 2010 09:30:41 +0100 [thread overview]
Message-ID: <4C6B9A31.9000706@ge.com> (raw)
In-Reply-To: <AANLkTinLbKUPNo=59RUUoznY7tYBh4LCacFeAgUEQ-6k@mail.gmail.com>
On 17/08/10 16:02, Cliff Brake wrote:
> I think it would be very useful to have a "stable" branch that is only
> synchronised with dev when X number of targets build from a clean
> build. It seems like this would be high value, with little effort.
> Of course there will be corner things that break, but at least a new
> beagleboard user can check out something and have reasonable
> confidence that it will build images.
>
> Does anyone have suggestions for the branch name and a reasonable
> subset of machines and build targets? Perhaps someone is already
> running these clean builds? At one point we had a machine at OSUOSL
> dedicated to this purpose, but no one ever set it up.
>
So something like Debian's stable, testing and unstable[1]?
Martyn
[1] http://www.debian.org/releases/
--
Martyn Welch (Principal Software Engineer) | Registered in England and
GE Intelligent Platforms | Wales (3828642) at 100
T +44(0)127322748 | Barbirolli Square,
Manchester,
E martyn.welch@ge.com | M2 3AB VAT:GB 927559189
next prev parent reply other threads:[~2010-08-18 9:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-14 15:46 What to do about the poor bitbake Quality Control? AJ ONeal
2010-08-14 16:16 ` J. L.
2010-08-14 17:06 ` AJ ONeal
2010-08-14 18:19 ` J. L.
2010-08-14 19:01 ` Frans Meulenbroeks
2010-08-14 19:04 ` Frans Meulenbroeks
2010-08-14 21:53 ` AJ ONeal
2010-08-15 7:27 ` Frans Meulenbroeks
2010-08-14 19:14 ` Philip Balister
2010-08-14 21:08 ` Elvis Dowson
2010-08-16 3:38 ` Gary Thomas
2010-08-17 15:02 ` Cliff Brake
2010-08-18 8:30 ` Martyn Welch [this message]
2010-08-15 21:22 ` Koen Kooi
2010-08-16 3:39 ` Gary Thomas
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=4C6B9A31.9000706@ge.com \
--to=martyn.welch@ge.com \
--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