Received: from vps892.directvps.nl (ikke.info [178.21.113.177]) by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id 03B20781A60 for <~alpine/devel@lists.alpinelinux.org>; Mon, 20 Jul 2020 17:06:39 +0000 (UTC) Received: by vps892.directvps.nl (Postfix, from userid 1008) id 2D613440122; Mon, 20 Jul 2020 19:06:39 +0200 (CEST) Date: Mon, 20 Jul 2020 19:06:39 +0200 From: Kevin Daudt To: Rasmus Thomsen Cc: Thomas Liske , ~alpine/devel@lists.alpinelinux.org Subject: Re: adding packages to stable Message-ID: <20200720170639.GA2616897@alpha> References: <82bd62b0-ddb0-f9ea-52a1-e94e54fa2044@fiasko-nw.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: On Mon, Jul 20, 2020 at 05:11:36PM +0200, Rasmus Thomsen wrote: > Hello, > > the procedure for adding new packages to a stable release are: > > 1. Make sure the package has a maintainer (if not, someone has to adopt > it) > 2. Move the package to community from testing. git mv testing/$pkgname > community/ and then git add community/$pkgname && git commit -m > "community/$pkgname: move from" should do the trick for that. Keep in > mind that all {make,}depends of the package also need to be in > community or main, packages in community can't pull in packages from > testing. > 3. Make a merge request > > However, new packages for community only end up in the next stable > release, so in this case it'd end up in 3.13. We want to avoid adding > new, potentially not well tested packages to new releases if posssible. > As such I'd recommend you to move things you want in a stable release, > tested and can maintain to community before the next stable release. > > I hope that helps, > > Rasmus Thomsen > > On Sun, 2020-07-19 at 16:06 +0200, Thomas Liske wrote: And to add to that, we do not have a backports repo like debian does, though, you could always build such a repo yourself with the packages you need. Kevin