On Thu, Sep 3, 2009 at 9:55 PM, Warren Baird<[email protected]> wrote:
> On Thu, Sep 3, 2009 at 3:47 PM, Nicola Mfb <[email protected]> wrote:
>>
>> Of course if the stabilization process is not on the road (I may guess
>> shr-import push to oe-devel will take some time), and unstable has to
>> be "usable" things are different.
>
> I understand that work is going on right now to update shr-testing, but I
> don't know how long the process is...
Oh! that's sound different from official plans, or it may be I did not
understand well.
AFAIK the roadmap should be:
*) shr-import pushed to openembedded-devel
*) unmeargable stuff goes to shr-unstable that will track oe-devel
(taking automagically the contribute of all the OE developers)
*) shr-testing will cherry pick tested commits from shr-unstable
*) at some point shr-stable will born from shr-testing and will cherry
pick only important fixes and backports from testing.
That (and more) was proposed by FSO coreteam.
Now if this is not true, or it simply delayed and will happen let's
say in 2 months, actual effort on shr-testing is a waste of time, and
will result in the nth testing image that at some point will be
unsupported.
But I'm beginning to feel stupid, having only to guess what's
happening following a dozens of different mailing list while real
informations are in private emails.
Please core shr/fso developers (and not only dos1 that actually is the
only public voice, thanks for his effort) clarify that for the entire
community, this is the hot topic of the month ;)
Nicola
_______________________________________________
Shr-User mailing list
[email protected]
http://lists.shr-project.org/mailman/listinfo/shr-user
