Re: [PATCH v2 2/5] include/hw/boards: cope with dev/rc versions in deprecation checks

[Thomas Huth <thuth@redhat.com>]

On 29/04/2025 15.15, Daniel P. Berrangé wrote:
> When VERSION is set to a development snapshot (micro >= 50), or a release
> candidate (micro >= 90) we have an off-by-1 in determining deprecation
> and deletion thresholds for versioned machine types. In such cases we need
> to use the next major/minor version in threshold checks.
> 
> This adapts the deprecation macros to do "next version" prediction when
> seeing a dev/rc version number.
> 
> This ensures users of release candidates get an accurate view of machines
> that will be deprecated/deleted in the final release.
> 
> This requires hardcoding our current release policy of 3 releases per
> year, with a major bump at the start of each year, and that dev/rc
> versions have micro >= 50.
> 
> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> ---
>   include/hw/boards.h | 33 ++++++++++++++++++++++++++++++++-
>   1 file changed, 32 insertions(+), 1 deletion(-)

Reviewed-by: Thomas Huth <thuth@redhat.com>