public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] taking a break from arches stabilization
Date: Mon, 10 Jul 2017 16:27:54 -0400	[thread overview]
Message-ID: <CAGfcS_kauyW2JE7uAnGFVOQzxrE4auyGWcHE8-aHs7tiqG3aXA@mail.gmail.com> (raw)
In-Reply-To: <025a124c-ef45-69f5-4cf2-47b636ef4d21@iee.org>

On Mon, Jul 10, 2017 at 4:05 PM, M. J. Everitt <m.j.everitt@iee.org> wrote:
>
> I dunno where you've been lately, Rich, but for most devs, would-be
> devs, and observers .. there -are- no arch teams left .. just a few Arch
> devs, or arch 'people' ..

Obviously.

I was describing how the arch team process worked when there were arch teams.

The fact that most arch teams are fairly defunct is the reason that
stable keywords have steadily been dropped.

>
> This is why stabilisation, if not for individual package maintainers on
> amd64, has become a joke, save for Ago's efforts, and recent efforts by
> kensington to streamline the effort for the likes of ago with his bot,
> and one or two other arch stabilisers (who I know exist, but not by name
> or nick).

Sure.  If nobody is maintaining stable keywords on an arch, then there
shouldn't be stable keywords on that arch, unless the stable keywords
are used for a different purpose and maintainers are free to downgrade
them at any time.

>
> There is no, and has not been, in the time I've been involved with
> Gentoo, any "pact" or "contract" between arch teams/devs and maintainers
> whatsoever, anything is only ever done as a 'favour' or if someone
> nudges the AT after the appropriate bug has been filed.
>

As a formal documented arrangement, no "pact" or "contract" has ever
existed between arch teams and maintainers.

However, this is basically the implicit basis for the system and the
consequence of our documented policies, such as the policy that
maintainers may not remove the highest stable version of a package.
These policies make no sense unless arch teams are held to a standard
of timely stabilization.

There has never been a need to document such a "contract" because the
Council has been maintaining it all along.  When people complain that
an arch team is unresponsive, the Council removes stable support for
the arch.

I'm describing reality here, not written policies.

-- 
Rich


  reply	other threads:[~2017-07-10 20:28 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-10 17:22 [gentoo-dev] taking a break from arches stabilization Agostino Sarubbo
2017-07-10 17:35 ` Alexis Ballier
2017-07-10 17:49 ` Rich Freeman
2017-07-10 19:57   ` Andrew Savchenko
2017-07-10 20:02     ` Rich Freeman
2017-07-10 20:17       ` Kristian Fiskerstrand
2017-07-10 23:29         ` Andrew Savchenko
2017-07-11 12:59           ` [gentoo-dev] " Michael Palimaka
2017-07-11 13:06             ` Rich Freeman
2017-07-11 13:47               ` Michael Palimaka
2017-07-11 14:13                 ` Kristian Fiskerstrand
2017-07-11 14:15                   ` Kristian Fiskerstrand
2017-07-11 14:21                     ` Michael Palimaka
2017-07-11 21:26                       ` Kristian Fiskerstrand
2017-07-11 22:13                         ` Thomas Deutschmann
2017-07-11 22:27                           ` Kristian Fiskerstrand
2017-07-12 13:19                             ` Marek Szuba
2017-07-11 23:12                           ` Mart Raudsepp
2017-07-12 11:59                         ` Michael Palimaka
2017-07-12 12:30                           ` Kristian Fiskerstrand
2017-07-12 14:13                             ` William Hubbs
2017-07-12 14:35                               ` Pacho Ramos
2017-07-11 14:25                     ` James Le Cuirot
2017-07-11 14:35                       ` Michael Palimaka
2017-07-11 14:43                         ` Rich Freeman
2017-07-11 14:16                   ` Michael Palimaka
2017-07-11 17:16                 ` William Hubbs
2017-07-12  0:03                   ` Sam Jorna (wraeth)
2017-07-10 18:11 ` [gentoo-dev] " Jonas Stein
2017-07-10 18:42 ` Mike Pagano
2017-07-10 19:09 ` Matt Turner
2017-07-10 19:53   ` Rich Freeman
2017-07-10 20:05     ` M. J. Everitt
2017-07-10 20:27       ` Rich Freeman [this message]
2017-07-10 23:54         ` Andrew Savchenko
2017-07-11 12:58           ` Rich Freeman
2017-07-11  0:48 ` Aaron Bauman
2017-07-11  8:32 ` Lars Wendler
2017-07-11 11:56   ` Agostino Sarubbo
2017-07-11 19:31 ` Daniel Campbell
2017-07-12 14:21 ` Sergey Popov

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=CAGfcS_kauyW2JE7uAnGFVOQzxrE4auyGWcHE8-aHs7tiqG3aXA@mail.gmail.com \
    --to=rich0@gentoo.org \
    --cc=gentoo-dev@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