From: Kent Fredric <kentnl@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: Mon, 15 Aug 2016 16:37:24 +1200 [thread overview]
Message-ID: <20160815163724.1b0aeebd@katipo2.lan> (raw)
In-Reply-To: <20160815162943.192f2605@katipo2.lan>
[-- Attachment #1: Type: text/plain, Size: 727 bytes --]
On Mon, 15 Aug 2016 16:29:43 +1200
Kent Fredric <kentnl@gentoo.org> wrote:
> > * The b.g.o workflow, bugs should not be considered fixed until the
> > fix has reached the stable tree. Today the InVCS keyword exists for
> > this purpose, but it is used to varying degree amongst developers.
> > Will a workflow change to introduce a new status, e.g RESOLVED
> > NeedsStable (name for illustration purpose only) incentivize
> > developers to not close bugs before it is fixed?
Also, if its already stable, the fix may go directly into stable.
Does this need to also spend time in "NeedsStable" state?
I'd assume not. But this is going to need clear definitions and lots of usecase
writeups.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-08-15 4:38 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 [this message]
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
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=20160815163724.1b0aeebd@katipo2.lan \
--to=kentnl@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