Received: from fx.arvanta.net (static-213-198-238-194.adsl.eunet.rs [213.198.238.194]) by nld3-dev1.alpinelinux.org (Postfix) with ESMTP id 56F97781DBD for <~alpine/devel@lists.alpinelinux.org>; Sun, 22 Mar 2020 17:37:11 +0000 (UTC) Received: from arya.arvanta.net (arya.arvanta.net [10.5.1.6]) by fx.arvanta.net (Postfix) with ESMTP id 32BAA42B6; Sun, 22 Mar 2020 18:37:10 +0100 (CET) Date: Sun, 22 Mar 2020 18:37:10 +0100 From: Milan =?utf-8?Q?P=2E_Stani=C4=87?= To: Thomas Liske Cc: ~alpine/devel@lists.alpinelinux.org Subject: Re: frr: moving to community Message-ID: <20200322173710.GA3814@arya.arvanta.net> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Hi Thomas, On Sun, 2020-03-22 at 18:28, Thomas Liske wrote: > Hi, > > I would like to see FRR moving from testing to community and wonder how that > works or how to trigger it politely. From my point of view it satisfies the > conditions found in [1] ("Before a package can move from testing to main or > community, the following requirements must be met:"). > > [1] https://wiki.alpinelinux.org/wiki/Aports_what_is_edge > > > Should I open a Bug or MR on gitlab.a.o or is there some other process I'm > not aware off? You can create MR or ask maintainer to create one. And you can open issue, of course, if you prefer -- Regards > > Regards, > Thomas