public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Palimaka <kensington@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: taking a break from arches stabilization
Date: Wed, 12 Jul 2017 00:16:29 +1000	[thread overview]
Message-ID: <832c1060-ce64-d0d8-c78a-93c84d39cade@gentoo.org> (raw)
In-Reply-To: <9069747f-2e1d-5573-e72d-f965deabb3c5@gentoo.org>

On 07/12/2017 12:13 AM, Kristian Fiskerstrand wrote:
> On 07/11/2017 03:47 PM, Michael Palimaka wrote:
>> The main risk of breakage of a package moving from testing to
>> stable is always at build time anyway.
> 
> citation needed
> 

Based on my experience doing package testing in stabilisation work. Feel
free to provide citations (or complete sentences) to the contrary.


  parent reply	other threads:[~2017-07-11 14:16 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 [this message]
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=832c1060-ce64-d0d8-c78a-93c84d39cade@gentoo.org \
    --to=kensington@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