From: Ulf Samuelsson <ulf_samuelsson@telia.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Plans for OE classic future
Date: Sat, 26 Nov 2011 19:53:06 +0100 [thread overview]
Message-ID: <4ED13592.3060506@telia.com> (raw)
In-Reply-To: <CA+M6bXmsbDoFS_8etRA+RYqkP7b0x8t998Tcmn9KyKhAbEP2ew@mail.gmail.com>
On 2011-11-26 16:20, Tom Rini wrote:
> On Sat, Nov 26, 2011 at 3:57 AM, Ulf Samuelsson
> <ulf_samuelsson@telia.com> wrote:
>> On 2011-11-25 23:04, Tom Rini wrote:
>>> On Fri, Nov 25, 2011 at 12:31 AM, Frans Meulenbroeks
>>> <fransmeulenbroeks@gmail.com> wrote:
>>>
>>>> After all, isn't one of the purposes of OE to promote information
>>>> sharing,
>>>> cooperation and the use of openembedded technology (and not make things
>>>> harder).
>>> One of the points of making master read-only would be to ensure that
>>> changes aren't lost.
>>>
>>> Perhaps the transition needs to be:
>>> - master is as it is today
>>> - master becomes oe-core backport || master-only bugfixes only
>>> - master becomes read only.
>>>
>>> And we go from the first step to the second step sometime sooner
>>> rather than later. The top of my head date would be before the
>>> paid-developers go on end of year breaks to try and make sure all the
>>> hobbyist folks start their hacking with oe-core+etc rather than master
>>> and risk getting caught later. I'm open to arguments on why that's
>>> exactly backwards...
>>>
>> Won't it be a problem for existing projects, if you cannot add fixes to cope
>> with new host OS versions.
>>
>> At the moment, openembedded-classic does not build properly with Ubuntu
>> 11.10 .
> Won't what be a problem? Either oe-core+meta-oe+etc fails on 11.10
> (so, fix it there first then backport changes) or it's fine and you
> can either find the relevant changes there and move them or it's a
> oe.dev-only bug and just needs to be fixed, under my proposal (until
> we reach the point where everyone is OK calling it r/o).
Making it R/O.
/Ulf
> And part of this is to say that yes, existing projects external to
> oe.dev need to move to oe-core(+meta-oe+whatever else) (where layers
> should be making their life easier or again, there's problems we're
> unaware of and need to be made aware of) or explain why they can't
> ever move (and are forking the project?).
>
--
Best Regards
Ulf Samuelsson
next prev parent reply other threads:[~2011-11-26 18:59 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AcyUlp+U2Tnulhz/TiaFJRlWYsvGkw==>
2011-10-27 10:53 ` Plans for OE classic future Mats Kärrman
2011-10-27 11:56 ` Henning Heinold
2011-10-27 12:27 ` Martin Jansa
2011-11-01 0:38 ` Ulf Samuelsson
2011-11-01 1:00 ` Denys Dmytriyenko
2011-11-01 7:13 ` Jaap de Jong
2011-11-01 10:39 ` Henning Heinold
2011-10-27 17:44 ` Denys Dmytriyenko
2011-10-27 23:56 ` Tom Rini
2011-11-23 20:46 ` Khem Raj
2011-11-23 21:18 ` Frans Meulenbroeks
2011-11-23 21:30 ` Philip Balister
2011-11-26 21:12 ` Bernhard Guillon
2011-11-27 9:15 ` Frans Meulenbroeks
2011-11-23 22:25 ` Khem Raj
2011-11-23 22:42 ` Andreas Oberritter
2011-11-24 8:03 ` Mats Kärrman
2011-11-24 10:23 ` Hauser, Wolfgang (external)
2011-11-24 11:12 ` Otavio Salvador
2011-11-24 11:24 ` Frans Meulenbroeks
2011-11-24 11:37 ` Otavio Salvador
2011-11-24 11:33 ` Paul Menzel
2011-11-24 11:43 ` Otavio Salvador
2011-11-24 17:45 ` Koen Kooi
2011-11-25 5:23 ` Raffaele Recalcati
2011-11-25 7:31 ` Frans Meulenbroeks
2011-11-25 10:45 ` Otavio Salvador
2011-11-25 22:04 ` Tom Rini
2011-11-26 10:57 ` Ulf Samuelsson
2011-11-26 15:20 ` Tom Rini
2011-11-26 15:49 ` Frans Meulenbroeks
2011-11-26 21:36 ` Tom Rini
2011-11-26 22:01 ` Paul Menzel
2011-11-26 22:33 ` Tom Rini
2011-11-26 22:49 ` Paul Menzel
2011-11-27 2:37 ` Tom Rini
2011-11-27 9:46 ` Koen Kooi
2011-11-27 10:12 ` Frans Meulenbroeks
2011-11-27 17:05 ` Tom Rini
2011-11-27 17:25 ` Frans Meulenbroeks
2011-11-27 18:25 ` Tom Rini
2011-11-27 21:58 ` Frans Meulenbroeks
2011-11-28 2:25 ` Tom Rini
2011-11-26 22:37 ` Raffaele Recalcati
2011-11-26 22:44 ` Otavio Salvador
2011-11-27 2:26 ` Tom Rini
2011-11-26 18:53 ` Ulf Samuelsson [this message]
2011-11-26 21:47 ` Tom Rini
2011-11-24 11:43 ` Paul Eggleton
2011-11-24 17:47 ` Koen Kooi
2011-11-24 18:15 ` Andreas Oberritter
2011-11-24 9:12 ` Koen Kooi
2011-11-24 9:31 ` Frans Meulenbroeks
2011-11-24 17:06 ` Khem Raj
2011-11-24 17:41 ` Andreas Oberritter
2011-11-24 18:43 ` Otavio Salvador
2011-11-25 13:17 ` Andreas Oberritter
2011-11-25 22:00 ` Tom Rini
2011-11-24 20:33 ` Paul Menzel
2011-11-25 21:43 ` Tom Rini
2011-11-26 16:11 ` Frans Meulenbroeks
2011-11-26 21:43 ` Tom Rini
2011-11-25 21:52 ` Tom Rini
2011-11-26 3:49 ` Denis 'GNUtoo' Carikli
2011-11-26 15:45 ` Frans Meulenbroeks
2011-11-26 16:56 ` Paul Menzel
2011-11-26 21:28 ` Tom Rini
2011-11-27 9:55 ` Frans Meulenbroeks
2011-11-27 17:15 ` Tom Rini
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=4ED13592.3060506@telia.com \
--to=ulf_samuelsson@telia.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.