From: Markos Chandras <hwoarang@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Slacker arches
Date: Tue, 25 Jan 2011 12:30:51 +0000 [thread overview]
Message-ID: <20110125123051.GB25322@Eternity.halls.manchester.ac.uk> (raw)
In-Reply-To: <4D3EC00D.3090001@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1474 bytes --]
On Tue, Jan 25, 2011 at 01:20:29PM +0100, "Paweł Hajdan, Jr." wrote:
> On 1/25/11 12:38 PM, Tomáš Chvátal wrote:
> > Every arch teams should stabilise OR write out reason why they can't do
> > so to stable bug in 90 days. If any arch team fails to do so the
> > maintainer can decide to drop their keywords to testing. Given depgraph
> > breakages the maintainer can coordinate with the QA team to drop all
> > reverse dependencies to testing too.
>
> Seconded. Reality++
>
> Be prepared for some issues though. Sometimes maintainers don't agree
> with reasons arch teams provide that block stabilizations. In those
> cases, who makes the decision? My suggestion is QA.
QA is not a solution to everything. The problem Tomas is trying to
counter here is the idle/slacking arches. If the arch is active but have some
concerns regarding the stabilization then let the maintainer deal with
it. This is the way we do it now anyway
>
> Also, we should have someone to check for stale stabilization bugs. I'm
> not sure if all reporters are able to take care of that, especially if
> they have a lot of bugs open.
>
> Paweł
>
Thats really their problem. Arches can always remove themselves from the
bugs. No need to care about stale bugs. If the maintainers don't care
then we(arches) don't care.
Regards,
--
Markos Chandras (hwoarang)
Gentoo Linux Developer
Key ID: B4AFF2C2
Key FP: 660A 0742 84EC 26F1 9EDB F00A FA83 5A15 B4AF F2C2
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-01-25 12:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-25 11:38 [gentoo-dev] Slacker arches Tomáš Chvátal
2011-01-25 12:05 ` Tomáš Chvátal
2011-01-25 12:20 ` "Paweł Hajdan, Jr."
2011-01-25 12:30 ` Markos Chandras [this message]
2011-01-30 18:12 ` "Paweł Hajdan, Jr."
2011-01-25 15:49 ` Jeremy Olexa
2011-01-25 15:56 ` Tomáš Chvátal
2011-01-26 2:14 ` [gentoo-dev] " Ryan Hill
2011-01-26 6:45 ` "Paweł Hajdan, Jr."
2011-01-28 7:31 ` [gentoo-dev] Status of sparc-fbsd, amd64-fbsd Torsten Veller
2011-01-28 13:38 ` Samuli Suominen
2011-02-11 6:53 ` [gentoo-dev] Re: Status of sparc-fbsd Torsten Veller
2011-02-11 20:16 ` Alexis Ballier
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=20110125123051.GB25322@Eternity.halls.manchester.ac.uk \
--to=hwoarang@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