public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ian Stakenvicius <axs@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: #wg-stable: Reservations about a "STABLE" & "NeedsStable" bugzilla keywords (re: [gentoo-dev] New Working Group established to evaluate the stable tree)
Date: Tue, 4 Oct 2016 13:25:49 -0400	[thread overview]
Message-ID: <8308d736-239c-c768-a5df-e1ffa0fe5e7e@gentoo.org> (raw)
In-Reply-To: <5f3541fe-960a-33e9-9373-e60e723e5263@gentoo.org>


[-- Attachment #1.1: Type: text/plain, Size: 1855 bytes --]

On 20/08/16 08:30 PM, Daniel Campbell wrote:
> On 08/15/2016 12:42 PM, Rich Freeman wrote:
>> On Mon, Aug 15, 2016 at 3:30 PM, Andreas K. Hüttel <dilfridge@gentoo.org> wrote:
>>> 1) Stabilization is a simpler and much more formalized process compared to
>>> normal bug resolution.
>>> * There is one version to be stabilized.
>>> * One precise package version
>>
>> Can you clarify what this means?  Do you mean that at any time only
>> one version of any particular package/slot is marked stable?
>>
>> That seems like it would be problematic for ranged deps.  Granted,
>> those are problematic in and of themselves since they can create
>> conflicts that are hard to resolve.  However, this extends conflicts
>> between package you might not want to install at the same time to
>> situations where you don't even need both of the conflicting packages.
>>
> I believe he's just talking about a per-bug or per-stablereq basis. So
> each version gets its own opportunity to have bugs surface or
> stabilization issues instead of attempting to stabilize a bunch of
> versions at once.
> 
> (Correct me if I'm wrong; I don't see the value of a single stable
> version for each package and it would create a lot of noise in git log)
> 

Even though some projects (mozilla, for instance) do request
stabilizations of multiple packages and/or versions in a single go,
that doesn't mean we should and I have no issues changing our process
to something more atomic.

What should be noted here is that if we work towards adopting new
tools or methods here, we absolutely need to do so in a way that is
beneficial to the workflow of our AT's, especially those that perform
large numbers of stabilizations like ago.  If this new process doesn't
make things at least incrementally easier for them, it needs to be
re-thought.



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 213 bytes --]

  reply	other threads:[~2016-10-04 17:26 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-14 21:35 [gentoo-dev] New Working Group established to evaluate the stable tree Kristian Fiskerstrand
2016-08-14 21:45 ` Ciaran McCreesh
2016-08-14 21:49   ` Kristian Fiskerstrand
2016-08-14 21:49   ` Kent Fredric
2016-08-14 21:52     ` M. J. Everitt
2016-08-14 22:06     ` Chris Reffett
2016-08-14 21:50   ` Anthony G. Basile
2016-08-14 21:57     ` Ciaran McCreesh
2016-08-14 22:01       ` Kent Fredric
2016-08-15 19:18       ` Andreas K. Hüttel
2016-08-15 19:19         ` Michael Orlitzky
2016-08-15  3:45 ` Jason Zaman
2016-08-15  3:53   ` Kent Fredric
2016-08-15  4:05     ` Jason Zaman
2016-08-15  7:55       ` Brian Dolbec
2016-08-15  8:50         ` Kent Fredric
2016-08-15 10:21         ` Kristian Fiskerstrand
2016-08-18  6:33           ` Daniel Campbell
2016-08-15 13:40         ` Rich Freeman
2016-08-15 15:48           ` Brian Dolbec
2016-08-15  4:29 ` #wg-stable: Reservations about a "STABLE" & "NeedsStable" bugzilla keywords (re: [gentoo-dev] New Working Group established to evaluate the stable tree) Kent Fredric
2016-08-15  4:37   ` Kent Fredric
2016-08-15 12:22     ` james
2016-08-15 12:49   ` Dirkjan Ochtman
2016-08-15 13:03     ` Kristian Fiskerstrand
2016-08-15 13:15       ` Dirkjan Ochtman
2016-08-15 13:25         ` Kristian Fiskerstrand
2016-08-15 14:28           ` james
2016-08-15 18:24           ` Dirkjan Ochtman
2016-08-15 19:30       ` Andreas K. Hüttel
2016-08-15 19:42         ` Rich Freeman
2016-08-21  0:30           ` Daniel Campbell
2016-10-04 17:25             ` Ian Stakenvicius [this message]
2016-10-07  2:40               ` Daniel Campbell
2016-08-15 23:00         ` Kent Fredric
2016-08-15 22:50       ` Kent Fredric
2016-08-15  8:00 ` [gentoo-dev] New Working Group established to evaluate the stable tree Pacho Ramos
2016-08-15  8:15   ` Pacho Ramos
2016-08-15 14:19   ` William Hubbs
2016-08-15 14:49     ` Kristian Fiskerstrand
2016-08-15 14:50       ` Kristian Fiskerstrand
2016-08-15 16:12         ` William Hubbs
2016-08-15 17:31           ` William Hubbs
2016-08-15 18:33             ` Rich Freeman
2016-08-15 19:12               ` William Hubbs
2016-08-15 19:27                 ` Rich Freeman
2016-08-15 20:01                   ` William Hubbs
2016-08-15 20:05                     ` Rich Freeman
2016-08-16  8:02                     ` [gentoo-dev] " Duncan
2016-08-16 13:52                       ` William Hubbs
2016-08-17  8:52                     ` [gentoo-dev] " Pacho Ramos
2016-08-17  8:50                   ` Pacho Ramos
2016-08-17 13:07                     ` Rich Freeman
2016-08-17 14:25                       ` Pacho Ramos
2016-08-18  7:32                     ` Raymond Jennings
2016-08-15 11:36 ` Kristian Fiskerstrand
2016-08-15 12:24 ` Michael Orlitzky
2016-08-15 13:37   ` Rich Freeman
2016-08-15 23:19     ` Kent Fredric
2016-08-15 19:33 ` Markus Meier

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=8308d736-239c-c768-a5df-e1ffa0fe5e7e@gentoo.org \
    --to=axs@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