Versioning and upgrade paths

Versioning and upgrade paths

[Koen Kooi]

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

Re: Versioning and upgrade paths

[Stefan Schmidt]

Hello.

On Sun, 2008-11-23 at 17:38, Koen Kooi wrote:
>
> 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.

Yeah, that was me. :)

Thanks for fixing. Read and understand the versioning policy now.

regards
Stefan Schmidt

Re: Versioning and upgrade paths

[Koen Kooi]

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