From: William Hubbs <williamh@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Call for agenda items - Council meeting 2016-08-14
Date: Fri, 5 Aug 2016 13:42:45 -0500 [thread overview]
Message-ID: <20160805184245.GA12055@whubbs1.gaikai.biz> (raw)
In-Reply-To: <971d2394-58dc-74e9-416c-90b3f9aaacb5@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1363 bytes --]
On Fri, Aug 05, 2016 at 07:31:33PM +0200, Kristian Fiskerstrand wrote:
> On 08/04/2016 06:24 PM, William Hubbs wrote:
> > I feel that our stable tree is so far behind on all
> > architectures that we are doing our stable users a disservice, so I
> > would like to open up a discussion here, and maybe some policy changes
> > at the next meeting.
>
> Far behind isn't necessarily a problem as long as it doesn't have bugs,
> in particular security related ones. Updating too often (without a good
> reason) can also be annoying enough.
>
> >
> > Ultimately, I think we need some form of automated stabilization, e.g.
> > if a package version sits in ~ for 30 days and there are no blockers at
> > that point, the new version should go automatically to stable on all
> > architectures where there is a previous stable version.
>
> I LOUDLY disagree. The stable tree should not be compromised by such
> automation, it is already bad enough without proper use-testing in some
> cases. Stable isn't only about building properly.
and that's why we don't commit straight to stable. people are supposed
to be testing those ~arch versions for a while before they go stable.
That testing should cover the use cases you are talking about and work
out the bugs. Once that's done, we should be able to move the package to
stable.
William
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2016-08-05 18:43 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
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 [this message]
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=20160805184245.GA12055@whubbs1.gaikai.biz \
--to=williamh@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