From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1RVMdP-0006Bc-Vb for garchives@archives.gentoo.org; Tue, 29 Nov 2011 12:18:04 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 9730DE0444; Tue, 29 Nov 2011 12:17:45 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id D14A721C0FC for ; Tue, 29 Nov 2011 12:17:11 +0000 (UTC) Received: from phjr-macbookpro.local (fi122.internetdsl.tpnet.pl [80.53.34.122]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: phajdan.jr) by smtp.gentoo.org (Postfix) with ESMTPSA id 82A4F1B401E for ; Tue, 29 Nov 2011 12:17:10 +0000 (UTC) Message-ID: <4ED4CD41.10402@gentoo.org> Date: Tue, 29 Nov 2011 13:17:05 +0100 From: =?UTF-8?B?IlBhd2XFgiBIYWpkYW4sIEpyLiI=?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:8.0) Gecko/20111105 Thunderbird/8.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] making the stable tree more up-to-date References: <4ECA0EA3.8020407@gentoo.org> <20111125163932.GH28718@schlaumatte.guest.mfo.de> In-Reply-To: <20111125163932.GH28718@schlaumatte.guest.mfo.de> X-Enigmail-Version: 1.3.3 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigC99063818233F90699F7DC8F" X-Archives-Salt: 89bddb14-1bf5-4ca0-90e2-49851c59dd20 X-Archives-Hash: ee9ca65ee44a036d4c88b2295649b9cf This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigC99063818233F90699F7DC8F Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 11/25/11 5:39 PM, Thomas Kahle wrote: > I still remember that arfrever had such a script running for python=20 > packages and that we were quite annoyed by the automatic stable bugs=20 > for every minor version of every small python package. I also still remember it, and that was one of the things that made me start the batch-stabilization workflow. I don't want to repeat frustration caused by that python script. If anyone's annoyed by my script or wants to opt out, please let me know. > For this reason I'm against running the script constantly. Packages=20 > with high release frequence upstream don't need every of their=20 > versions to be stabilized. If a package has been in the tree for 180 days, I guess we're safe. I'm going to only consider the last ~arch package as stabilization candidate, as requested by various maintainers. > Personally, I think they don't even need every of their versions=20 > bumped... IMHO nothing wrong with it, and it can even be a good thing if given team has manpower to keep up. Of course it's way more important to fix bugs in existing packages than to bump every minor version. > On the other hand, having a big stable frenzy once every few months=20 > seems good for exactly the reasons you name. Good, I think I still need to figure out the best way to run my script. I'm leaning towards a more continuous fashion instead of a huge frenzy from time to time. Each run can be limited (in fact I've limited the last one to just 100 bugs), and in fact for my next run I'm seriously considering filing _less_ bugs. Partially because Agostino (ago) reported lots of problems with existing stabilization candidates, and I think it's worth to fix them before next round of stabilizations. :) --------------enigC99063818233F90699F7DC8F Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) iEYEARECAAYFAk7UzUIACgkQuUQtlDBCeQK+egCfcRZKIMdxOsRnUNMhyyESZEUc UxMAn2L2GxbGEO2DmkFtGjh3q7XJP51f =dQR3 -----END PGP SIGNATURE----- --------------enigC99063818233F90699F7DC8F--