From: Thomas Liske <thomas@fiasko-nw.net>
Subject: adding packages to stable
To: ~alpine/devel@lists.alpinelinux.org
Message-ID: <82bd62b0-ddb0-f9ea-52a1-e94e54fa2044@fiasko-nw.net>
Date: Sun, 19 Jul 2020 16:06:05 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
 Thunderbird/68.10.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Spam_bar: -

Hi,

I wonder if there is any policy about adding packages from edge (main or 
community) to a stable branch. (In Debian this would not be allowed but 
they have the backports repository which could be used for that.)

For non-binary packages (i.e. pure python stuff) it is possible to use 
package pinning to use packages from edge on a stable release. But this 
might break for binary packages due to linking against libraries etc.

Using edge package pinning feels to unstable for me to use them on 
productive systems (read: running a stable release) since the staging 
from edge to stable is missing. There seems to be a low chance of 
breaking something in stable by just adding *new* packages.


Example: Would a merge request adding the ifstate package to 3.12 
accepted (and what (commit|MR) title should I use)?


TIA,
Thomas