[OE-core] Yocto Project 1.2 M4 schedule

[Anders Darander]

On Thu, Apr 12, 2012 at 21:46, Philip Balister <philip at balister.org> wrote:
> On 04/12/2012 11:40 AM, Richard Purdie wrote:
>> On Thu, 2012-04-12 at 14:32 -0300, Otavio Salvador wrote:
>>> On Thu, Apr 12, 2012 at 14:22, Koen Kooi <koen at dominion.thruhere.net> wrote:
>>>> 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.
>>>
>>> I think layers ought to have tags for both ...
>>>
>>> <layer>-oe-core-<tag>
>>> <layer>-yocto-<tag>
>>
>> This would be rather sad if it were necessary. The whole point is we're
>> trying to build things which are compatible with each other. If that
>> turns out not to be the case I want to fix it, not encourage it.
>
> We need a coherent tag name to use across layers. The Yocto Project is
> the umbrella project, so using the yocto-project in the tag name is a
> good way to show this coordination among projects to people not familiar
> with how things are working. (As Koen notes, this makes communication
> with people whose primary exposure to the Yocto Project is watching
> youtube videos)

I'm also in favor of a yocto-project-1.2 tag, for the same reason as
Koen and Philip mention. That would make it easier communicating with
customers and PHB's that has heard of Yocto Project...

> I do not want to see table containing Yocto Project release information
> and they relate to a set of seemingly random tags in other layers.

The risk for this is definitely somewhat higher with a strict YYYY-XX
release tag (which also might collide with other projects/layer more
easily). Thus, I'm advocating a 'yocto-project'-prefix for the tags in
question.

/Anders