From: Marcin Juszkiewicz <marcin@juszkiewicz.com.pl>
To: openembedded-devel@openembedded.org
Subject: RFC: new stable release
Date: Tue, 17 Mar 2009 15:38:17 +0100 [thread overview]
Message-ID: <200903171538.21499.marcin@juszkiewicz.com.pl> (raw)
[-- Attachment #1: Type: text/plain, Size: 2548 bytes --]
Hi
I know that there were lot of talks about creating stable branch of
OpenEmbedded in last months. But we need stable branch for vendors which
use our product.
As some people know I am working for Bug Labs company. Their product
named 'BUG Linux' is based on Poky 'pinky' (last stable release). We
were considering switch to newer (but never released) version named
'elroy' but recently we decided to switch to OpenEmbedded.
But to what kind of OE? Development branch change every day and things
break from time to time, packages get version bumps without notifying
anyone etc. Other possibility would be switch to stable branch but
current one is deprecated and not maintained anymore.
So the situation looks like we will need new stable branch with few
maintainers (I will be one of them) and with proper policies for merging
updates from development tree of OE. I maintained OE branches used for
OpenZaurus/Familiar few years ago so can say that I have needed
experience for it.
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).
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.
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.
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.
What do you feel about it? Any opinions or suggestions? Want to join
effort?
Regards,
--
JID: hrw@jabber.org
Website: http://marcin.juszkiewicz.com.pl/
LinkedIn: http://www.linkedin.com/in/marcinjuszkiewicz
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 204 bytes --]
next reply other threads:[~2009-03-17 14:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-17 14:38 Marcin Juszkiewicz [this message]
2009-03-17 14:50 ` RFC: new stable release Koen Kooi
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=200903171538.21499.marcin@juszkiewicz.com.pl \
--to=marcin@juszkiewicz.com.pl \
--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