Re: [openstack-dev] [nova] Wishlist bugs == (trivial) blueprint?

ber <rochelle.gro...@huawei.com> > To: "OpenStack Development Mailing List (not for usage questions)" > <openstack-dev@lists.openstack.org> > Date: 03/18/2016 12:46 AM > Subject: Re: [openstack-dev] [nova] Wishlist bugs == (trivial) blueprint? > > (Inline because the ma

Re: [openstack-dev] [nova] Wishlist bugs == (trivial) blueprint?

On 3/17/2016 1:26 PM, Tim Bell wrote: On 17/03/16 18:29, "Sean Dague" wrote: On 03/17/2016 11:57 AM, Markus Zoeller wrote: Suggested action items: 1. I close the open wish list items older than 6 months (=138 reports) and explain in the closing comment that they are

Re: [openstack-dev] [nova] Wishlist bugs == (trivial) blueprint?

> <openstack-dev@lists.openstack.org> > Date: 03/17/2016 04:57 PM > Subject: Re: [openstack-dev] [nova] Wishlist bugs == (trivial) blueprint? > > Top post as I summarize below what was said. At the end is a proposal > of actions. > > TL;DR: Use the ope

Re: [openstack-dev] [nova] Wishlist bugs == (trivial) blueprint?

(Inline because the mail formatted friendly this time) From: Tim Bell March 17, 2016 11:26 AM: On 17/03/16 18:29, "Sean Dague" wrote: >On 03/17/2016 11:57 AM, Markus Zoeller wrote: > >> Suggested action items: >> >> 1. I close the open wish list items older than 6 months (=138

Re: [openstack-dev] [nova] Wishlist bugs == (trivial) blueprint?

On 03/17/2016 11:57 AM, Markus Zoeller wrote: > Suggested action items: > > 1. I close the open wish list items older than 6 months (=138 reports) >and explain in the closing comment that they are outdated and the >ML should be used for future RFEs (as described above). > 2. I post on

Re: [openstack-dev] [nova] Wishlist bugs == (trivial) blueprint?

On 17/03/16 18:29, "Sean Dague" wrote: >On 03/17/2016 11:57 AM, Markus Zoeller wrote: > >> Suggested action items: >> >> 1. I close the open wish list items older than 6 months (=138 reports) >>and explain in the closing comment that they are outdated and the >>ML

Re: [openstack-dev] [nova] Wishlist bugs == (trivial) blueprint?

hie...@openstack.org> > To: openstack-dev@lists.openstack.org > Date: 03/16/2016 11:27 AM > Subject: Re: [openstack-dev] [nova] Wishlist bugs == (trivial) blueprint? > > Sean Dague wrote: > > It's a trade off. Would you rather keep Wishlist mechanism and have ~30 > >

Re: [openstack-dev] [nova] Wishlist bugs == (trivial) blueprint?

How do other teams capture feature requests outside of the blueprint/spec process? I'm inclined to agree with the others about the bug queue not being the right place for it, as someone who has been assisting with bug queue maintenance. I also agree with the other points brought up that we

Re: [openstack-dev] [nova] Wishlist bugs == (trivial) blueprint?

Sean Dague wrote: It's a trade off. Would you rather keep Wishlist mechanism and have ~30 extra bugs in every release, and have to hunt for a new bug lead twice as often? That's my gut feel on the break down here. To get the bug backlog under control, we have to make hard calls here. This is

Re: [openstack-dev] [nova] Wishlist bugs == (trivial) blueprint?

On Tue, Mar 15, 2016 at 05:59:32PM +, Tim Bell wrote: [...] > The bug process was very light weight for an operator who found > something they would like enhanced. It could be done through the web > and did not require git/gerrit knowledge. I went through the process > for a change: > > -

Re: [openstack-dev] [nova] Wishlist bugs == (trivial) blueprint?

On 03/15/2016 04:09 PM, melanie witt wrote: > On Mar 15, 2016, at 10:59, Tim Bell wrote: > >> The risk I see is that we are missing input to the development process in >> view of the complexity of submitting those requirements. Clearly, setting >> the bar too low means that

Re: [openstack-dev] [nova] Wishlist bugs == (trivial) blueprint?

On Mar 15, 2016, at 10:59, Tim Bell wrote: > The risk I see is that we are missing input to the development process in > view of the complexity of submitting those requirements. Clearly, setting the > bar too low means that there is no clear requirement statement etc.

Re: [openstack-dev] [nova] Wishlist bugs == (trivial) blueprint?

wrote: -To: openstack-dev@lists.openstack.orgFrom: Matt Riedemann <mrie...@linux.vnet.ibm.com>Date: 03/15/2016 02:50PMSubject: Re: [openstack-dev] [nova] Wishlist bugs == (trivial) blueprint?On 3/15/2016 8:37 AM, Chris Dent wrote:> On Tue, 15 Mar 2016, Markus Zoeller wrote:>>&g

Re: [openstack-dev] [nova] Wishlist bugs == (trivial) blueprint?

On 15/03/16 16:21, "Markus Zoeller" <mzoel...@de.ibm.com> wrote: >Sean Dague <s...@dague.net> wrote on 03/15/2016 02:52:47 PM: > >> From: Sean Dague <s...@dague.net> >> To: openstack-dev@lists.openstack.org >> Date: 03/15/2016 02:53 PM

Re: [openstack-dev] [nova] Wishlist bugs == (trivial) blueprint?

On Tue, 15 Mar 2016, Markus Zoeller wrote: Chris Dent wrote on 03/15/2016 03:23:42 PM: My take is that if we do have that level of friction then influence, in its many forms, will solely be mediated by the vendors that consume the upstream OpenStack community, or people

Re: [openstack-dev] [nova] Wishlist bugs == (trivial) blueprint?

Chris Dent <cdent...@anticdent.org> wrote on 03/15/2016 03:23:42 PM: > From: Chris Dent <cdent...@anticdent.org> > To: "OpenStack Development Mailing List (not for usage questions)" > <openstack-dev@lists.openstack.org> > Date: 03/15/2016 03:24 PM > S

Re: [openstack-dev] [nova] Wishlist bugs == (trivial) blueprint?

Sean Dague <s...@dague.net> wrote on 03/15/2016 02:52:47 PM: > From: Sean Dague <s...@dague.net> > To: openstack-dev@lists.openstack.org > Date: 03/15/2016 02:53 PM > Subject: Re: [openstack-dev] [nova] Wishlist bugs == (trivial) blueprint? > > On 03/15/2

Re: [openstack-dev] [nova] Wishlist bugs == (trivial) blueprint?

Chris Dent <cdent...@anticdent.org> wrote on 03/15/2016 02:37:45 PM: > From: Chris Dent <cdent...@anticdent.org> > To: "OpenStack Development Mailing List (not for usage questions)" > <openstack-dev@lists.openstack.org> > Date: 03/15/2016 02:38 PM > S

Re: [openstack-dev] [nova] Wishlist bugs == (trivial) blueprint?

On Tue, 15 Mar 2016, Matt Riedemann wrote: We do have a way for people to drop off RFEs/ideas for features without actually providing design details, which is the backlog specs: https://specs.openstack.org/openstack/nova-specs/specs/backlog/index.html In what universe is writing a backlog

Re: [openstack-dev] [nova] Wishlist bugs == (trivial) blueprint?

Le 15/03/2016 14:48, Matt Riedemann a écrit : On 3/15/2016 8:37 AM, Chris Dent wrote: On Tue, 15 Mar 2016, Markus Zoeller wrote: Long story short, I'm in favor of abandoning the use of "wishlist" as an importance in bug reports to track requests for enhancements. While I'm very much in

Re: [openstack-dev] [nova] Wishlist bugs == (trivial) blueprint?

On 03/15/2016 09:37 AM, Chris Dent wrote: > On Tue, 15 Mar 2016, Markus Zoeller wrote: > >> Long story short, I'm in favor of abandoning the use of "wishlist" >> as an importance in bug reports to track requests for enhancements. > > While I'm very much in favor of limiting the amount of time

Re: [openstack-dev] [nova] Wishlist bugs == (trivial) blueprint?

On 3/15/2016 8:37 AM, Chris Dent wrote: On Tue, 15 Mar 2016, Markus Zoeller wrote: Long story short, I'm in favor of abandoning the use of "wishlist" as an importance in bug reports to track requests for enhancements. While I'm very much in favor of limiting the amount of time issues (of

Re: [openstack-dev] [nova] Wishlist bugs == (trivial) blueprint?

On Tue, 15 Mar 2016, Markus Zoeller wrote: Long story short, I'm in favor of abandoning the use of "wishlist" as an importance in bug reports to track requests for enhancements. While I'm very much in favor of limiting the amount of time issues (of any sort) linger in launchpad[1] I worry

[openstack-dev] [nova] Wishlist bugs == (trivial) blueprint?

Long story short, I'm in favor of abandoning the use of "wishlist" as an importance in bug reports to track requests for enhancements. The reason I bring this up is [1] which I closed as invalid because I saw it as a RFE. jichenjc disagreed with my approach there. I'm asking here on the ML to