From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: Branched for release
Date: Thu, 01 Oct 2015 16:42:28 +0100 [thread overview]
Message-ID: <1443714148.14733.17.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAP9ODKoL6bWh7Z9AYHLC-tzh6MbCtsPuEBf=-gYdbi7K0kABqQ@mail.gmail.com>
On Thu, 2015-10-01 at 11:41 -0300, Otavio Salvador wrote:
> I agree.
>
> The mix between codenames and version numbers cause a lot of confusion
> for outsiders. We, involved with the project development can handle it
> (even though sometimes I ask myself if one codename is older or newer
> than another) but for outsiders it is deadly confusing.
As I've just replied to Khem, I posted a fairly comprehensive look at
all the possible options quite a while back, the last time people
complained. Basically, we can't win. We have slowly killed off all the
numbers that didn't have a purpose so we have one naming scheme and one
number that corresponds to it.
The only real exception is bitbake, which as tool with its own
release/versions, makes sense.
I'd also highlight that now is not the time to start changing the
release process.
Cheers,
Richard
next prev parent reply other threads:[~2015-10-01 15:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 14:24 Branched for release Richard Purdie
2015-10-01 14:28 ` Khem Raj
2015-10-01 14:41 ` Otavio Salvador
2015-10-01 15:42 ` Richard Purdie [this message]
2015-10-01 15:03 ` Carlos Alberto Lopez Perez
2015-10-01 15:23 ` Khem Raj
2015-10-01 15:37 ` Richard Purdie
2015-10-01 17:24 ` Khem Raj
2015-10-01 20:25 ` Richard Purdie
2015-10-01 20:28 ` Khem Raj
2015-10-02 1:37 ` Khem Raj
2015-10-01 20:30 ` Otavio Salvador
2015-10-01 21:16 ` Richard Purdie
2015-10-02 1:46 ` Khem Raj
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=1443714148.14733.17.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio.salvador@ossystems.com.br \
/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.