[OE-core] Yocto Project 1.2 M4 schedule

[Koen Kooi]

Op 12 apr. 2012, om 18:55 heeft Khem Raj het volgende geschreven:

> On Thu, Apr 12, 2012 at 2:29 AM, Koen Kooi <koen at dominion.thruhere.net> wrote:
>> 
>> Op 12 apr. 2012, om 11:02 heeft Richard Purdie het volgende geschreven:
>> 
>>> On Wed, 2012-04-11 at 01:51 +0100, Julian Pidancet wrote:
>>>> On 04/09/12 19:01, Liu, Song wrote:
>>>>> Hi all,
>>>>> 
>>>>> This is to restate and clarify the schedule for Yocto Project 1.2 M4 (milestone 4). If you are concerned or have patches you would like to merge, please see the following dates:
>>>>> 
>>>>> 1. RC3 official patch cut-off time: 12:00AM April 8th, 2012, PDT
>>>>> 2. RC3 build: April 11th, 2012, PDT
>>>>> 3. RC4 official patch cut-off time: 12:00AM April 15th, 2012, PDT
>>>>> 4. RC4 build: April 18th, 2012, PDT
>>>>> 5. YP 1.2 release: April 27th, 2012, PDT
>>>>> 
>>>>> You can also check out the schedule here: https://www.google.com/calendar/embed?height=600&wkst=1&bgcolor=%23FFFFFF&src=mg0m150m30gs891eqqhtfu5jgg%40group.calendar.google.com&color=%238C500B&src=sc7rov4ck552t2f0pav120t7r0%40group.calendar.google.com&color=%23528800&src=theyoctoproject%40gmail.com&color=%23182C57&ctz=America%2FLos_Angeles
>>>>> 
>>>>> Please feel free to let me and Beth know if you have any concerns or questions.
>>>>> 
>>>>> Thanks!
>>>>> Song
>>>>> PM, Yocto Project
>>>> 
>>>> Hi,
>>>> 
>>>> I don't see any commits tagged for these milestones in
>>>> git.openembedded.org/openembedded-core at the moment. Will there be a
>>>> release tag or a release branch created on the git repository when YP
>>>> 1.2 comes out, to indicate people that there's a "stable" version of
>>>> oe-core they can use ?
>>> 
>>> Yes, there will be a branch created on OE-Core.
>>> 
>>> At this point the actual branch naming/tagging is a little in flux.
>>> There was some discussion about this at collaboration summit and the BSP
>>> summit but there was no conclusion.
>>> 
>>> I've tried to write an email on the subject and it basically goes around
>>> in circles. Ideally we need a scheme which can be used in all the layers
>>> which doesn't contain numbers as these may conflict with various layer
>>> schemes. The poky release names at least do that. Ideally people also
>>> want something sortable with more context such as the year. Doing this
>>> without numbers is harder.
>> 
>> I'm still a big fan of using 'yoctoproject-1.2' as substring for tags and branches. The objections I heard to that didn't make sense to me, but I see this as a purely technical matter where others see it as something different :)
>> 
> 
> I think that string is fine as long as its just for yocto but I think
> for OE-Core we are going to do a General release
> so tagging that with something yocto project will be very confusing
> unless we plan to do different releases of OE-Core for general
> availability
> and yocto project. I dont think we have bandwidth for that. And since
> poky repository makes a copy of OE-Core metadata it can be tagged in
> yoctoproject specific tags
> 
> since OE-Core is at center of all layers I would propose that other
> layers when tagged contain OE-Core's release tag in their own tags
> name
> 
> so something like <layer-tag>-<OE-Core-tag its targetting>

You just volunteered to handle all the "Does it work with yocto 1.2?" questions :) 

Simply put: people are stupid, they need explicit PHB compliant names in tags, even if it isn't 100% politically correct to say "yocto" when we actually mean "oe-core".

Unless the yocto 1.2 release note state that it's based on oe-core "foo" and all layers compatible with "foo" use "foo" in tags/branches.