From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: OE stable, testing, dev (was Re: What to do about the poor bitbake Quality Control?)
Date: Sat, 21 Aug 2010 06:31:30 -0600 [thread overview]
Message-ID: <4C6FC722.9060002@mlbassoc.com> (raw)
In-Reply-To: <AANLkTinzw_8N9fu5bpuT17zcjffqWJ3ZH9rLK1cA-yG9@mail.gmail.com>
On 08/21/2010 12:26 AM, Frans Meulenbroeks wrote:
> 2010/8/18 Cliff Brake<cliff.brake@gmail.com>:
>> On Wed, Aug 18, 2010 at 4:30 AM, Martyn Welch<martyn.welch@ge.com> wrote:
>>> 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]?
>>
>> That sounds good to me -- so how about org.openembedded.dev and
>> org.openembedded.testing branches?
>
> Good plan!
>
>>
>> I'll plan to start doing a clean build of dev every Monday for the
>> Beagleboard, and then merge to testing once it builds. Initial
>> targets:
>
> Cool!
>>
>> Angstrom Distro
>> beagleboard/beagleboard-linuxtag2010-demo-image
>> x86/minimal-image
>
> It would be nice to have some additional distro's (e.g. minimal, shr)
> and machines (what would be a good coverage here) tested before it is
> pushed
>>
>> My workstation runs a 64-bit OS, so that is probably worst case
>> (compared to i686).
>>
> What OS? If you want to make things really nasty go to RHEL4 (but I
> think most people would be fine with e.g. ubuntu 10.04)
> Ideally you'd do this in a clean vm to make sure that there is no
> dependency on whatever happens to be installed on your workstation for
> other purposes.
Perhaps share this load? I'd volunteer to make some tests using
my Fedora servers.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
prev parent reply other threads:[~2010-08-21 12:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-18 15:07 OE stable, testing, dev (was Re: What to do about the poor bitbake Quality Control?) Cliff Brake
2010-08-18 16:11 ` Jason Kridner
2010-08-18 17:05 ` Frans Meulenbroeks
2010-08-20 0:02 ` Denys Dmytriyenko
2010-08-21 5:53 ` Esben Haabendal
2010-08-23 8:45 ` Koen Kooi
2010-08-18 17:15 ` Khem Raj
2010-08-19 9:33 ` OE stable, testing, dev Florian Boor
2010-08-21 6:26 ` OE stable, testing, dev (was Re: What to do about the poor bitbake Quality Control?) Frans Meulenbroeks
2010-08-21 12:31 ` Gary Thomas [this message]
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=4C6FC722.9060002@mlbassoc.com \
--to=gary@mlbassoc.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 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.