Precedence: list
MIME-Version: 1.0
From: Carlo Landmeter <clandmeter@gmail.com>
Date: Wed, 17 Aug 2016 12:47:43 +0200
Message-ID: <CA+cSEmPgTq6OGXheiNhBwsmwcNDfiXfjmFoC7Szr6Ws8_WBMGw@mail.gmail.com>
Subject: [alpine-devel] Cleanup of testing repository
To: Alpine-devel <alpine-devel@lists.alpinelinux.org>
Content-Type: multipart/alternative; boundary=089e011767effe5b44053a42314a

--089e011767effe5b44053a42314a
Content-Type: text/plain; charset=UTF-8

Hi,

I have been rebuilding world for our new aarch64 architecture. While main
and community repositories are in good shape, testing really is not.
We currently have 1832 aports in testing of which 437 fail to build:
http://tpaste.us/GVV8

I would like to purge packages from testing that have not had any update
since x days, this will reduce the list of failed packages, and will make
it easier to get testing in building shape again.
As an example you can find a list of not updated packages since 1 jan 2016
here: http://tpaste.us/36aa

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. And please remember testing is not a copy of AUR, our developers
should no be responsible for other peoples mess in testing.

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.

-carlo

--089e011767effe5b44053a42314a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi,<div><br></div><div>I have been rebuilding world for ou=
r new aarch64 architecture. While main and community repositories are in go=
od shape, testing really is not.</div><div>We currently have 1832=C2=A0apor=
ts in testing of which 437 fail to build: <a href=3D"http://tpaste.us/GVV8"=
>http://tpaste.us/GVV8</a></div><div><br></div><div>I would like to purge p=
ackages from testing that have not had any update since x days, this will r=
educe the list of failed packages, and will make it easier to get testing i=
n building shape again.</div><div>As an example you can find a list of not =
updated packages since 1 jan 2016 here:=C2=A0<a href=3D"http://tpaste.us/36=
aa">http://tpaste.us/36aa</a></div><div><br></div><div>We should determine =
what the best possible TTL is for packages in testing. It should be long en=
ough so developers get a chance to get their packages fixed upstream and sh=
ort enough to prevent the mess we currently have.</div><div>My suggestion w=
ould be something between 6 and 12 months, but i&#39;m open to ideas. And p=
lease remember testing is not a copy of AUR, our developers should no be re=
sponsible for other peoples mess in testing.=C2=A0</div><div><br></div><div=
>To keep testing healthy we can purge them every time we create a new relea=
se branch, this is also a good time for developers to check testing and get=
 things moved to community if they want to keep it.<br></div><div><br></div=
><div>-carlo</div></div>

--089e011767effe5b44053a42314a--


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---