public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: William Hubbs <williamh@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Call for agenda items - Council meeting 2013-09-10
Date: Thu, 29 Aug 2013 15:03:38 -0500	[thread overview]
Message-ID: <20130829200338.GA5780@linux1> (raw)
In-Reply-To: <CAB9SyzSN80MUNkHMmshPyy23aiQ=qdYU+cNh_FQAfgmr5Rb5mQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1514 bytes --]

All, I'm responding to this particular message because I think there is
another  sub-thread we should think about.

On Thu, Aug 29, 2013 at 09:16:03PM +0800, Ben de Groot wrote:
> On 29 August 2013 14:09, Michael Weber <xmw@gentoo.org> wrote:
> > On 08/28/2013 01:15 PM, Markos Chandras wrote:
> >> The feedback on the original question was mostly positive.
> >> Most people agree that the long stabilization queues for these
> >> architectures create problems
> >> for maintainers wishing to drop old versions.
> > Is this the only motivation? Drop all the effort that has been put into
> > stabilization work on minor arches just for some impatient maintainers?
> >
> > Keywording/Stabilization is a process we all agreed on joining, so live
> > with it.
> 
> Minor arches holding up GLSAs and removal of vulnerable stable ebuilds
> for 3 months or more is *not* acceptable, and not something I agreed
> to when joining...
> 
> If they can't even do security stabilizations in a reasonable
> timeframe, they have no business being considered stable arches.

In the past, I have had arch teams refuse to stabilize a newer version
of a package after an older version is stable unless a user of the arch
wants the new version to be stabilized, thus forcing  older versions to be
kept around for their stable users.

IMO if an arch team does this, maintainers should be able to move
the affected package to ~ on that arch, or maybe even drop that arch's
keyword entirely.

William


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2013-08-29 20:03 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-27  9:54 [gentoo-project] Call for agenda items - Council meeting 2013-09-10 Ulrich Mueller
2013-08-27  9:59 ` [gentoo-project] " Ulrich Mueller
2013-08-27 14:15   ` Ian Stakenvicius
2013-08-27 14:27   ` Michał Górny
2013-08-28 11:15 ` [gentoo-project] " Markos Chandras
2013-08-28 11:24   ` Rich Freeman
2013-08-28 17:28     ` Matt Turner
2013-08-28 17:39       ` Ian Stakenvicius
2013-08-28 12:52   ` Samuli Suominen
2013-08-28 17:35   ` Andreas K. Huettel
2013-08-29  6:09   ` Michael Weber
2013-08-29  8:32     ` Markos Chandras
2013-08-29 11:22       ` Michael Weber
2013-08-29 13:16     ` Ben de Groot
2013-08-29 13:33       ` Markos Chandras
2013-08-29 15:34       ` Jack Morgan
2013-08-29 15:57         ` Andreas K. Huettel
2013-08-30  8:52           ` Sergey Popov
2013-08-30 12:53             ` Chris Reffett
2013-09-18 12:32               ` [gentoo-project] " Steven J. Long
2013-08-29 16:06         ` [gentoo-project] " Rich Freeman
2013-08-29 15:56       ` Andreas K. Huettel
2013-08-29 16:15       ` Matt Turner
2013-08-29 16:25         ` Matt Turner
2013-08-29 20:03       ` William Hubbs [this message]
2013-08-29 15:22   ` Jack Morgan
2013-08-29 15:44     ` Rich Freeman
2013-08-29 16:06       ` Andreas K. Huettel
2013-08-29 17:49         ` Rich Freeman
2013-09-15 11:41           ` Rich Freeman
2013-09-17 13:04             ` [gentoo-project] Minor arches (was: Call for agenda items - Council meeting 2013-09-10) Ulrich Mueller
2013-09-17 17:40               ` Matt Turner
2013-09-17 18:56               ` Agostino Sarubbo
2013-08-29 17:17     ` [gentoo-project] Call for agenda items - Council meeting 2013-09-10 Pacho Ramos
2013-08-29 18:33       ` Tom Wijsman
2013-08-29 19:40         ` Tom Wijsman
2013-08-29 20:23         ` Andreas K. Huettel
2013-09-15 15:03       ` Rich Freeman
2013-09-15 15:21         ` Michał Górny
2013-09-15 15:22         ` Pacho Ramos
2013-09-15 19:03           ` Rich Freeman
2013-09-18  2:53             ` Daniel Campbell
2013-09-18  6:51               ` Pacho Ramos
2013-09-18  7:19               ` Sergey Popov
2013-09-18  8:02               ` Daunting developer process? (was Re: [gentoo-project] Call for agenda items - Council meeting) 2013-09-10 Sven Vermeulen
2013-09-18  8:40                 ` Markos Chandras
2013-09-18 12:18                 ` [gentoo-project] Re: Daunting developer process? (was " Steven J. Long
2013-09-18 13:55                   ` Tom Wijsman
2013-09-18 10:42               ` [gentoo-project] Call for agenda items - Council meeting 2013-09-10 heroxbd
2013-09-19  4:33                 ` Daniel Campbell
2013-09-19  6:07                   ` Pacho Ramos
2013-09-19 13:21                     ` Daniel Campbell
2013-09-19 19:35                       ` Pacho Ramos
2013-09-19 10:09                   ` Dirkjan Ochtman
2013-09-19 12:37                   ` Tom Wijsman
2013-09-19 13:33                     ` Daniel Campbell
2013-09-15 19:08         ` Ciaran McCreesh
2013-09-15 20:18           ` Rich Freeman
2013-08-28 12:46 ` hasufell
2013-08-28 13:18   ` Ulrich Mueller
2013-08-28 14:04     ` hasufell
2013-08-28 17:02       ` Ulrich Mueller
2013-08-29  2:09         ` Patrick Lauer
2013-08-29 11:21           ` Rich Freeman
2013-08-29 13:37             ` hasufell
2013-09-03  9:20 ` [gentoo-project] " Ulrich Mueller

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=20130829200338.GA5780@linux1 \
    --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