From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: Versioning and upgrade paths
Date: Mon, 01 Dec 2008 10:35:12 +0100 [thread overview]
Message-ID: <gh0b4g$jeq$1@ger.gmane.org> (raw)
In-Reply-To: <ggc0uc$kvv$1@ger.gmane.org>
this applies to '2.6.28rc6' as well:
http://cgit.openembedded.net/cgit.cgi?url=openembedded/commit/&id=4ed5900e8d4a41241a6b26f530673f7815beec1e
On 23-11-08 17:38, Koen Kooi wrote:
> Hi,
>
> I noticed people adding recipes with PVs in the form of '2.6.28rc4',
> which is wrong:
>
> '2.6.28rc4' will sort higher than '2.6.28', so upgrading to the release
> from the RC will be impossible.
>
> Now some people will start arguing that kernel upgrades using a package
> manager shouldn't be done, but that's not the point. An upgrade path
> should always be provided, even if the distro/user/developer will choose
> to not use it.
>
> The wiki page about the OE versioning policy has background information
> and samples on how to contruct a proper PV:
>
> http://wiki.openembedded.net/index.php/Versioning_Policy
>
> regards,
>
> Koen
prev parent reply other threads:[~2008-12-01 9:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-23 16:38 Versioning and upgrade paths Koen Kooi
2008-11-23 17:04 ` Stefan Schmidt
2008-12-01 9:35 ` Koen Kooi [this message]
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='gh0b4g$jeq$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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