From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: testing branch 2010-08-23
Date: Thu, 26 Aug 2010 13:50:47 -0600 [thread overview]
Message-ID: <4C76C597.9050302@mlbassoc.com> (raw)
In-Reply-To: <AANLkTim6-d4krhcMuAZojQVNdy3W-m_ON-mOvK5y3tqn@mail.gmail.com>
On 08/23/2010 05:49 PM, Cliff Brake wrote:
> Hello,
>
> As detailed in the following page, we are trying to get a testing
> branch going where we try to verify OE builds for a number of
> combinations of distro/machine/target/
>
> http://wiki.openembedded.net/index.php/Testing
>
> I have branched dev.oe.org to the testing-testing branch, and have
> verified it builds the following.
>
> beagleboard angstrom-2008.1 beagleboard-linuxtag2010-demo-image
> Ubuntu 10.04 64-bit User:Cbrake
> beagleboard angstrom-2008.1 console-image Ubuntu 10.04 64-bit User:Cbrake
To be clear, a line with an entry in the 'last tested' column indicates a
successful build of that combination?
> Next Monday, we will merge testing-testing to the testing branch, and
> tag it with the testing_2010-08-23 tag, and note the combinations that
> build in the above wiki page.
>
> We are looking for people who are willing to test clean builds of
> other combinations on a regular basis, or other ideas on how to make
> this "testing" concept work. My initial thought is to work on a
> weekly cycle, but of course not every combination will be tested every
> week.
>
> If this gains enough traction, perhaps we will want to make the
> testing branch the default OE meta-data branch so that new users by
> default get something that will probably build. I think its also very
> useful to give users a known starting point. With the myriad of
> combinations available, its useful to know what is a good baseline.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2010-08-26 22:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-23 23:49 testing branch 2010-08-23 Cliff Brake
2010-08-24 14:32 ` Stefan Schmidt
2010-08-24 14:58 ` Chris Larson
2010-08-27 15:04 ` Cliff Brake
2010-08-27 15:21 ` Chris Larson
2010-08-26 19:50 ` Gary Thomas [this message]
2010-08-26 20:10 ` Cliff Brake
2010-08-26 20:23 ` Gary Thomas
2010-08-26 23:20 ` Graham Gower
2010-08-27 3:45 ` Khem Raj
2010-08-27 4:12 ` Graham Gower
2010-08-27 6:50 ` Frans Meulenbroeks
2010-08-27 14:45 ` Cliff Brake
2010-08-27 14:36 ` Cliff Brake
2010-08-31 6:12 ` Steffen Sledz
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=4C76C597.9050302@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox