From: Rich Freeman <rich0@gentoo.org>
To: Kristian Fiskerstrand <k_f@gentoo.org>
Cc: gentoo-dev <gentoo-dev@lists.gentoo.org>, bugzilla@gentoo.org
Subject: Re: [gentoo-dev] [RFC] bugs.g.o: Killing VERIFIED state, possibly introducing STABILIZED
Date: Fri, 17 Jun 2016 12:41:25 -0400 [thread overview]
Message-ID: <CAGfcS_=Kyjuo_fvaf6qwcwGCVxMQ+Qs6Q7zy_bg_zu23d6UiGg@mail.gmail.com> (raw)
In-Reply-To: <1656f2a7-eee0-6aa2-7687-c3e568453c00@gentoo.org>
On Fri, Jun 17, 2016 at 12:00 PM, Kristian Fiskerstrand <k_f@gentoo.org> wrote:
> On 06/17/2016 03:58 PM, Rich Freeman wrote:
>>
>> That could actually be generalized. I could see many types of bugs
>> where the issue is with upstream, and we might want to track the
>> progress as upstream implements a fix, releases it, and then it is
>> stabilized on Gentoo. So, maybe we need another state to track in
>> upstream's VCS vs the Gentoo repo.
>
> For a great deal of this we have UPSTREAM keyword, and also combination
> with PATCH keyword if we've submitted an own patch.
Usually we mean UPSTEAM to mean that the issue is an upstream issue,
and should be pursued there. Usually we don't use it to mean that the
issue IS resolved upstream but we're waiting for a release/etc. I'm
not sure how important the distinction is in practice. The portage
team could of course use it differently.
--
Rich
next prev parent reply other threads:[~2016-06-17 16:41 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-16 13:02 [gentoo-dev] [RFC] bugs.g.o: Killing VERIFIED state, possibly introducing STABILIZED Michał Górny
2016-06-16 13:14 ` Kristian Fiskerstrand
2016-06-16 13:19 ` James Le Cuirot
2016-06-16 13:20 ` Kristian Fiskerstrand
2016-06-16 14:00 ` M. J. Everitt
2016-06-17 13:52 ` Michał Górny
2016-06-17 13:58 ` Rich Freeman
2016-06-17 14:00 ` Alexander Berntsen
2016-06-17 14:02 ` Michał Górny
2016-06-17 16:00 ` Kristian Fiskerstrand
2016-06-17 16:41 ` Rich Freeman [this message]
2016-06-17 16:46 ` Kristian Fiskerstrand
2016-06-17 17:05 ` Brian Dolbec
2016-06-17 17:26 ` Kristian Fiskerstrand
2016-06-17 17:39 ` Rich Freeman
2016-06-19 22:00 ` Raymond Jennings
2016-06-16 13:18 ` Davide Pesavento
2016-06-16 13:25 ` Andrew Savchenko
2016-06-16 14:51 ` Kent Fredric
2016-06-16 21:57 ` Andreas K. Huettel
2016-06-16 22:05 ` Kristian Fiskerstrand
2016-06-17 7:37 ` Alexander Berntsen
2016-06-17 7:50 ` Michał Górny
2016-06-17 7:55 ` Alexander Berntsen
2016-06-17 7:58 ` Kristian Fiskerstrand
2016-06-17 11:50 ` Rich Freeman
2016-06-17 11:58 ` Kristian Fiskerstrand
2016-06-17 12:18 ` Rich Freeman
2016-06-17 13:02 ` Kristian Fiskerstrand
2016-06-17 13:26 ` Kristian Fiskerstrand
2016-06-17 13:48 ` Rich Freeman
2016-06-17 15:33 ` Kristian Fiskerstrand
2016-06-17 16:43 ` Rich Freeman
2016-06-16 21:58 ` Andreas K. Huettel
2016-06-17 9:02 ` Michał Górny
2016-06-17 9:12 ` Alexander Berntsen
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='CAGfcS_=Kyjuo_fvaf6qwcwGCVxMQ+Qs6Q7zy_bg_zu23d6UiGg@mail.gmail.com' \
--to=rich0@gentoo.org \
--cc=bugzilla@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=k_f@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