X-Original-To: alpine-devel@lists.alpinelinux.org Received: from newmail.tetrasec.net (unknown [172.21.74.12]) by lists.alpinelinux.org (Postfix) with ESMTP id 966945C4212 for ; Thu, 18 Aug 2016 01:02:15 +0000 (GMT) Received: from ncopa-macbook.copa.dup.pw (unknown [50.233.46.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: n@tanael.org) by newmail.tetrasec.net (Postfix) with ESMTPSA id 625D35A0838; Thu, 18 Aug 2016 01:02:15 +0000 (GMT) Date: Wed, 17 Aug 2016 18:02:14 -0700 From: Natanael Copa To: Carlo Landmeter Cc: Alpine-devel Subject: Re: [alpine-devel] Cleanup of testing repository Message-ID: <20160817180214.797158fd@ncopa-macbook.copa.dup.pw> In-Reply-To: References: X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.28; x86_64-alpine-linux-musl) X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Wed, 17 Aug 2016 12:47:43 +0200 Carlo Landmeter wrote: > We should determine what the best possible TTL is for packages in testing. > It should be long enough so developers get a chance to get their packages > fixed upstream and short enough to prevent the mess we currently have. > My suggestion would be something between 6 and 12 months, but i'm open to > ideas. I wouldn't mind if try keep it short. > And please remember testing is not a copy of AUR, our developers > should no be responsible for other peoples mess in testing. Yes. The idea with testing was originally to test that the package built on the build server environment and not only on the developers'. Also, sometimes we build packages that we don't use ourselves, so we needed a way for the requester to test that the package actually works before we moved it to the repository. Unfortunately we often never get any feedback on the packages requested so we don't know if it actually works or not, and the packaged ends up in testing forever. > To keep testing healthy we can purge them every time we create a new > release branch, this is also a good time for developers to check testing > and get things moved to community if they want to keep it. Agree. I think we also did a cleanup when we branched 3.4-stable. We might need to start cleaning it more often. -nc --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---