From: Marek Szuba <marecki@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Call for agenda items - Council meeting 2016-08-14
Date: Mon, 8 Aug 2016 14:35:36 +0200 [thread overview]
Message-ID: <52993bd4-afc9-197e-acda-96db413e6608@gentoo.org> (raw)
In-Reply-To: <20160805153658.GA11058@whubbs1.gaikai.biz>
[-- Attachment #1.1: Type: text/plain, Size: 1242 bytes --]
On Fri, Aug 05, 2016 at 10:36:41AM -0400, Rich Freeman wrote:
> No argument, but if you actually asked stable users I'm not convinced
> that they'd prefer less-tested recent packages over well-tested older
> ones. Anything to get things fresher is good, but there probably
> needs to be some kind of sanity check.
My two cents on the subject. Perhaps I am odd in this but in spite of
having been messing with ebuild development I keep my Gentoo systems
mostly stable - and I definitely prefer keeping it this way. This might
perhaps have something to do with the fact I do not really need the
latest and supposedly greatest versions of all packages, for instance
the amd64 box I am writing this on has only got 15 entries (plus
dependencies of those) in my "version bump" Portage keyword files.
That said, the situation gets much worse for packages which can be found
*only* in ~arch - on the same box the "not in stable" keyword file
contains 72 entries. Only a few of these have been orphaned so I guess I
could always submit a lot of STABLEREQs but telling the truth, the
number has really discouraged me.
Bottom line: I would say we do need some way of streamlining ebuild
stabilisation.
Cheers,
--
MS
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-08-08 12:35 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-04 14:15 [gentoo-project] Call for agenda items - Council meeting 2016-08-14 Kristian Fiskerstrand
2016-08-04 16:24 ` William Hubbs
2016-08-04 17:08 ` Dirkjan Ochtman
2016-08-04 17:09 ` Brian Dolbec
2016-08-04 18:31 ` William Hubbs
2016-08-04 20:12 ` Andrew Savchenko
2016-08-04 22:22 ` William Hubbs
2016-08-04 23:25 ` Rich Freeman
2016-08-05 2:26 ` William Hubbs
2016-08-05 10:57 ` Rich Freeman
2016-08-05 14:28 ` William Hubbs
2016-08-05 14:36 ` Rich Freeman
2016-08-05 15:36 ` William Hubbs
2016-08-08 12:35 ` Marek Szuba [this message]
2016-08-08 19:51 ` Pacho Ramos
2016-08-09 2:07 ` Jack Morgan
2016-08-09 5:32 ` Kent Fredric
2016-08-09 5:59 ` Rich Freeman
2016-08-09 10:05 ` Kent Fredric
2016-08-09 14:41 ` Brian Dolbec
2016-08-09 15:12 ` Kent Fredric
2016-08-09 16:15 ` Brian Dolbec
2016-08-09 17:09 ` Kent Fredric
2016-08-09 17:12 ` Brian Evans
2016-08-09 17:18 ` Chí-Thanh Christopher Nguyễn
2016-08-09 17:22 ` Ciaran McCreesh
2016-08-09 20:08 ` Rich Freeman
2016-08-09 20:14 ` Kristian Fiskerstrand
2016-08-09 20:20 ` Kristian Fiskerstrand
2016-08-10 1:15 ` Pallav Agarwal
2016-08-10 1:28 ` Brian Dolbec
2016-08-05 17:32 ` Kristian Fiskerstrand
2016-08-05 17:29 ` Kristian Fiskerstrand
2016-08-04 21:30 ` Daniel Campbell
2016-08-05 16:11 ` Michael Orlitzky
2016-08-05 16:22 ` [gentoo-project] " Michael Palimaka
2016-08-05 17:06 ` Michael Orlitzky
2016-08-05 17:11 ` Chí-Thanh Christopher Nguyễn
2016-08-05 17:38 ` Michael Orlitzky
2016-08-05 17:19 ` Michał Górny
2016-08-05 17:21 ` Michael Orlitzky
2016-08-05 17:31 ` [gentoo-project] " Kristian Fiskerstrand
2016-08-05 18:42 ` William Hubbs
2016-08-05 18:45 ` Kristian Fiskerstrand
2016-08-05 18:55 ` NP-Hardass
2016-08-05 19:03 ` Kristian Fiskerstrand
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52993bd4-afc9-197e-acda-96db413e6608@gentoo.org \
--to=marecki@gentoo.org \
--cc=gentoo-project@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox