Re: [PATCH] glep-0068: Add <straight-to-stable/> element to metadata.xml

Jay Faulkner <[email protected]>
Newsgroups gmane.linux.gentoo.devel
Message-ID <[email protected]>
On 5/9/26 2:33 AM, Arthur Zamarin wrote:
> Add a new <straight-to-stable/> element to metadata.xml, which indicates
> that stable keywords should be retained on version bumps (i.e. as
> a recommendation for developers, which may be overridden if
> stabilization is deemed inappropriate).
> 
> For example, various `*-bin` packages are meaningless to wait for
> stabilization, and should be stabilized immediately. This information
> is only available when looking at the package's history and detecting
> if the maintainer was bumping the version with stable keywords retained.
> 
> Various developer helper tools can be updated to detect this element
> and not destable the ebuild on version bumps. The developer is always
> free to override this recommendation if they feel that a wait period is
> necessary.
> 
> Closes: https://bugs.gentoo.org/974436
> Signed-off-by: Arthur Zamarin <[email protected]>
> ---
>   glep-0068.rst | 13 ++++++++++---
>   1 file changed, 10 insertions(+), 3 deletions(-)
> 
> diff --git a/glep-0068.rst b/glep-0068.rst
> index f822c6e..2d74c09 100644
> --- a/glep-0068.rst
> +++ b/glep-0068.rst
> @@ -4,10 +4,11 @@ Title: Package and category metadata
>   Author: Michał Górny <[email protected]>
>   Type: Standards Track
>   Status: Final
> -Version: 1.4
> +Version: 1.5
>   Created: 2016-03-14
> -Last-Modified: 2023-02-22
> -Post-History: 2016-03-16, 2018-02-20, 2022-05-22, 2022-10-07, 2023-02-22
> +Last-Modified: 2026-05-09
> +Post-History: 2016-03-16, 2018-02-20, 2022-05-22, 2022-10-07, 2023-02-22,
> +              2026-05-09
>   Content-Type: text/x-rst
>   Requires: 67
>   Replaces: 34, 46, 56
> @@ -162,6 +163,12 @@ element can contain, in any order:
>     after arch testing on one of them (i.e. if the package is known to be fully
>     arch-independent).
>   
> +- zero or more ``<straight-to-stable/>`` elements, possibly restricted
> +  to specific package versions (at most one for each version) whose presence
> +  indicates that stable keywords should be retained on version bumps (i.e. as
> +  a recommendation for developers, which may be overridden if stabilization is
> +  deemed inappropriate).
> +
>   - zero or more ``<use/>`` elements containing USE flag descriptions
>     in different languages (at most one for each language), as detailed
>     in `USE flag descriptions`_.


+1 I would use this on a package I currently maintain.

Thanks for the suggestion,
JayF
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.