From: Denys Dmytriyenko <denis@denix.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Yocto Project 1.2 M4 schedule
Date: Thu, 12 Apr 2012 17:13:30 -0400 [thread overview]
Message-ID: <20120412211330.GG13291@denix.org> (raw)
In-Reply-To: <DE32AA93-7E17-480C-9027-DB6EA6F2A0C0@dominion.thruhere.net>
On Thu, Apr 12, 2012 at 09:57:02PM +0200, Koen Kooi wrote:
>
> Op 12 apr. 2012, om 21:46 heeft Philip Balister het volgende geschreven:
>
> > 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@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 do not want to see table containing Yocto Project release information
> > and they relate to a set of seemingly random tags in other layers.
> >
> > Philip
> >
> > PS: For various reasons, the tag needs to be yocto-project.... not yocto....
>
> "yoctoproject", without the hyphen to be consistent with the domainname :)
Technically, yocto-project.org is a valid domain name too, as it properly
redirects to yoctoproject.org and both are registered by the Linux Foundation.
Should we put it to vote? While we still have time before the release, we need
to agree on the naming eventually.
--
Denys
next prev parent reply other threads:[~2012-04-12 21:23 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-09 18:01 Yocto Project 1.2 M4 schedule Liu, Song
2012-04-11 0:51 ` Julian Pidancet
2012-04-12 9:02 ` Richard Purdie
2012-04-12 9:29 ` Koen Kooi
2012-04-12 14:24 ` Otavio Salvador
2012-04-12 14:39 ` Koen Kooi
2012-04-12 14:51 ` Eric Bénard
2012-04-12 15:45 ` McClintock Matthew-B29882
2012-04-12 18:28 ` Denys Dmytriyenko
2012-04-12 16:55 ` Khem Raj
2012-04-12 17:12 ` Otavio Salvador
2012-04-12 17:22 ` Koen Kooi
2012-04-12 17:32 ` Otavio Salvador
2012-04-12 18:31 ` Denys Dmytriyenko
2012-04-12 19:39 ` Flanagan, Elizabeth
2012-04-12 18:40 ` Richard Purdie
2012-04-12 19:20 ` Otavio Salvador
2012-04-12 19:46 ` Philip Balister
2012-04-12 19:57 ` Koen Kooi
2012-04-12 21:13 ` Denys Dmytriyenko [this message]
2012-04-12 21:16 ` Otavio Salvador
2012-04-12 21:29 ` Phil Blundell
2012-04-13 7:33 ` Andrei Gherzan
2012-04-13 10:58 ` Anders Darander
2012-04-12 19:31 ` Julian Pidancet
2012-04-12 19:41 ` Denys Dmytriyenko
2012-04-18 9:28 ` Koen Kooi
2012-04-18 10:18 ` Yocto Project Branch/Release Naming Richard Purdie
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=20120412211330.GG13291@denix.org \
--to=denis@denix.org \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox