From: Kristian Fiskerstrand <k_f@gentoo.org>
To: gentoo-dev@lists.gentoo.org, Michael Palimaka <kensington@gentoo.org>
Subject: Re: [gentoo-dev] Re: taking a break from arches stabilization
Date: Wed, 12 Jul 2017 14:30:34 +0200 [thread overview]
Message-ID: <75c94306-b7f5-03a3-fd8e-8b883f43d0f9@gentoo.org> (raw)
In-Reply-To: <690840bf-5be9-89a5-8570-4b26daa6d422@gentoo.org>
[-- Attachment #1.1: Type: text/plain, Size: 632 bytes --]
On 07/12/2017 01:59 PM, Michael Palimaka wrote:
> If it's not a stable candidate then why do you use this as an example
> against build testing-based stabilisations? If there are known issues it
> should never reach the arch teams in the first place.
This might be the crux of things, as long as automatic stabilization is
not triggered by some set of rules (e.g 30 days in ~arch) , and still
requires manual trigger by, preferably, the maintainer there is likely
no issue.
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2017-07-12 12:30 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 [this message]
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
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=75c94306-b7f5-03a3-fd8e-8b883f43d0f9@gentoo.org \
--to=k_f@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=kensington@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