[svsm-devel] [RFC] COCONUT-SVSM Release Process

[Jörg Rödel]

Hi Daniel,

On Tue, Nov 05, 2024 at 11:40:44AM +0000, Daniel P. Berrangé wrote:
> At the RPM packaging level,  the "R" release will always compare as
> newer than the "D" release, simply because the "R" is larger than
> "D" in ascii.

Do you expect development and stable releases within the same package
stream? My expectation is that distributions package the stable and
development releases with different package names (e.g. coconut-svsm vs.
coconut-svsm-unstable).

> If you use a "NN" counter instead of month, then you can follow the
> approach that even numbers are stable releases and odd numbers are
> development releases. This is a simple rule to understand and has
> well defined version comparison behaviour

Okay, that is another option. I find that slightly less intuitive, but
since other projects do it this way I might be wrong with this and we
actually don't need to intensively teach users about that sheme.

Regards,

-- 
Jörg Rödel
jroedel at suse.de

SUSE Software Solutions Germany GmbH
Frankenstraße 146
90461 Nürnberg
Germany
https://www.suse.com/

Geschäftsführer: Ivo Totev, Andrew McDonald, Werner Knoblich
(HRB 36809, AG Nürnberg)