From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: RFC: new stable release
Date: Tue, 17 Mar 2009 15:50:43 +0100 [thread overview]
Message-ID: <gpodc3$nos$1@ger.gmane.org> (raw)
In-Reply-To: <200903171538.21499.marcin@juszkiewicz.com.pl>
On 17-03-09 15:38, Marcin Juszkiewicz wrote:
> Which things needs defining? I have few in mind:
>
> 1. Adding new things. This should be possible only by backporting from
> OE.dev tree and needs to be Acked by at least 2-3 developers which
> use stable branch. New code has to build for at least one distro and
> ARM+x86 architectures (unless it is related to one arch or even one
> machine).
So things must get tested before committing, right?
> 2. Marking recipes as buildable or not. With over 6000 of them it is
> really hard to check everything for status. We can remove many old
> versions but sometimes they are useful for some projects. I would
> rather add things like BUILDABLE_armv4t = "1" into recipe or into
> conf/distro/include/${DISTRO}-status.inc file. Similar status for
> recipes which are known to not work for some archs.
Just have a CSV file that includes the test coverage for package +
machines. We can have one per distro. If needed we can extract the info
from tinderbox after we've done a few builds.
> 3. Dealing with non buildable stuff. We have 'nonworking' and 'obsolete'
> dirs in metadata - both should be dropped in stable branch. Other
> recipes can be marked as not buildable or dropped from branch - I did
> not thought yet on it.
That does mean you can't easily resurrect recipes, but seeing that only
happens once every 5 years or so..
> 4. Lifetime of branch. Will we do new stable release after 6 months or
> after one year? For how long stable branch will be supported by OE
> itself? I know that there will be companies which will provide
> support for longer time - thats what I do with Poky 'pinky' now.
The previous branch had a 12 + 3 month lifecycle, 12 months of support
then 3 months to wind down.
> What do you feel about it? Any opinions or suggestions? Want to join
> effort?
I certainly want to join the effort, but I fear that creating a stable
branch might make some people more inclined to dump even worse crap in
.dev, which would not be a good thing. So *if* we go with a stable
branch we should make sure .dev well be in a good shape as well.
regards,
Koen
next prev parent reply other threads:[~2009-03-17 14:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-17 14:38 RFC: new stable release Marcin Juszkiewicz
2009-03-17 14:50 ` Koen Kooi [this message]
2009-03-17 15:15 ` Mathieu Chouinard
2009-03-17 15:23 ` Marcin Juszkiewicz
2009-03-17 15:09 ` Matteo Fortini
2009-03-17 15:25 ` Mike (mwester)
2009-03-17 16:35 ` Tom Rini
2009-03-17 17:06 ` Shane Dixon
2009-03-17 17:26 ` Tom Rini
2009-03-17 15:39 ` Richard Purdie
2009-03-17 17:42 ` Philip Balister
-- strict thread matches above, loose matches on Subject: below --
2009-03-17 15:04 Marco Cavallini
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='gpodc3$nos$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--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