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 1RbXq1-0005FO-Mb for garchives@archives.gentoo.org; Fri, 16 Dec 2011 13:28:38 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 4C7B021C11C; Fri, 16 Dec 2011 13:28:17 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id DAAE321C0F0 for ; Fri, 16 Dec 2011 13:27:40 +0000 (UTC) Received: from phjr-macbookpro.home (abne59.neoplus.adsl.tpnet.pl [83.7.250.59]) (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 5F6081B40AF for ; Fri, 16 Dec 2011 13:27:39 +0000 (UTC) Message-ID: <4EEB4742.5000302@gentoo.org> Date: Fri, 16 Dec 2011 14:27:30 +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> <4EEB2087.2050608@gentoo.org> In-Reply-To: <4EEB2087.2050608@gentoo.org> X-Enigmail-Version: 1.3.3 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigD93CB6C3E31F215D5BF9AC19" X-Archives-Salt: d5017ae6-b40f-42be-9588-13684a7a52aa X-Archives-Hash: 0e1409194d4bbbf72b32a3d52839fcc4 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigD93CB6C3E31F215D5BF9AC19 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 12/16/11 11:42 AM, justin wrote: > I really like that you open all those bugs. But it makes no sense to > add arches after a "time out". At least not after a such a short=20 > one. I'm sorry this has annoyed/upset you. Let me just point out some facts: - in November I first wrote about this new "more stabilizations" thing, and included a list of ~800 packages, including many sci- ones (). I don't remember any complains from the sci- maintainers then. - people complain that a week-long timeout is too short, while after I CC arches the answer often comes within minutes. - actually in this case you've said "go ahead" for the bugs filed (thank you!), so I don't fully understand the concerns here - the bugs get filed when a package's most recent version has spent 6 months in ~arch, has _no_ open bugs, and is not a beta/alpha/rc/whatever version. Many packages for which I filed bugs spent in ~arch a year or mo= re. > The maintainer is responsible for the package, that means it is > their responsibility to decide that a package should go stable. Packages with stable versions a year behind suggest this is not always the case. Furthermore, most maintainers are happy about those stabilizations (or tools), and users also like it. > In addition they have to make the package fit to the standards that=20 > the arch teams request. There are standards and nits. We frequently stabilize a package if only nits are present. > So as long as you don't review the packages yourself, consider a > different proceeding than this timeout. See the conditions above that packages have to meet to be included in the stabilization list. I consider that an adequate review, and I know arch developers and testers who look at the ebuilds. It's always possible to close the bug if the package is deemed not ready.= > Please remove all added arches from the packages maintained by all=20 > sci* teams. I can do that, but are you sure? I noted you've commented "go ahead" on many of those (thank you!) - how about those bugs? --------------enigD93CB6C3E31F215D5BF9AC19 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) iEYEARECAAYFAk7rR0cACgkQuUQtlDBCeQKkUgCffUfczhTPTpeYo6mM11owr6bm aG8AnAk2lwh8nUsfoLuGHwpHhIfeLVzJ =s8tQ -----END PGP SIGNATURE----- --------------enigD93CB6C3E31F215D5BF9AC19--