Date: Fri, 16 Jul 2021 17:22:02 -0500 (CDT)
From: Ariadne Conill <ariadne@dereferenced.org>
To: alpine@vodafonemail.de
cc: u.alpine.devel@lists.alpinelinux.org
Subject: Re: have next stable (e.g. v3.15) as transitional symlink to edge
 in the repository?
In-Reply-To: <271ced6b60f44bb4ba2718e811337a70@vodafonemail.de>
Message-ID: <35bd34e-1481-487-40ad-428a25ad4833@dereferenced.org>
References: <271ced6b60f44bb4ba2718e811337a70@vodafonemail.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed

Hello,

On Fri, 16 Jul 2021, alpine@vodafonemail.de wrote:

>
> Hi,
> sometimes I'd wish it could be possible to let a system only temporarily follow
> edge development, but stay on the next stable release when it gets out.

To be clear: the contents of the Alpine edge repository *never* become a 
release.  Once in a while, we take the Alpine edge repository, and use 
that as the basis of a distro-wide rebuild to create a new release branch.

Mixing edge and the next release once it is branched is not recommended, 
in the same way that mixing edge and the current/older releases is not 
recommended.

> Could you enable this (simply) within some release script, by having it create
> an additional symlink for the next stable release (e.g. /v3.15) in the
> repositories that would poindt to /edge? (In addition to creating/replacing
> he new latest-stable and vX.Y release locations.)

No, because it will create problems: users will follow v3.15 and get edge, 
then will not be properly upgraded to v3.15 release when it occurs, unless 
they explicitly use `apk upgrade --available`.

Ariadne