[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-release-team
Subject:    Re: [RFC] Bugzilla "Feature" Severity
From:       Allen Winter <winter () kde ! org>
Date:       2012-07-19 13:10:19
Message-ID: 10424923.Wcqs6axJ9e () jiffy
[Download RAW message or body]


For the record, I just created a request for this:
https://bugs.kde.org/show_bug.cgi?id=303794


On Saturday, July 14, 2012 08:34:43 AM Allen Winter wrote:
> On Friday, July 13, 2012 05:22:06 PM todd rme wrote:
> > On Fri, Jul 13, 2012 at 7:43 AM, Martin Gräßlin <mgraesslin@kde.org> wrote:
> > > On Thursday 12 July 2012 19:15:10 Allen Winter wrote:
> > >> We would do away with the wiki-based feature plans currently on techbase:
> > >> replacing with a bugzilla query.
> > >> 
> > >> For example, the query for all wishes planned for 4.10 are:
> > >> https://bugs.kde.org/buglist.cgi?bug_severity=wishlist&target_milestone=4
> > >> .10
> > >> 
> > >> but I am proposing:
> > >> https://bugs.kde.org/buglist.cgi?bug_severity=feature&target_milestone=4.
> > >> 10
> > >> 
> > >> Comments?
> > > 
> > > +1 would love it, especially the feature plan through bugzilla query.
> > > 
> > > Cheers
> > > Martin
> > 
> > I like the idea.
> > 
> > As an alternative, however, what about using the same naming scheme we
> > use in the release feature list, i.e "Todo", "In Progress", and
> > "Complete"?  This could allow the bugzilla list to be directly
> > translated into a feature plan.
> > 
> 
> Of course,  the feature owner is responsible for setting the appropriate bug status.
> Should be easier to change the Status field in bko than modifiying the wiki, slightly.
> 
> But you're correct,  we would need to translate:
>   New => Todo
>   Assigned => In Progress
>   Resolved => Done
> 
> Also, I sorta like having the features grouped by module as the wiki page does now.
> 
> I could easily write a program to convert the query output to be more pleasing
> but that defeats the purpose of having an automatic thing.
> 
> I don't know anything about bugzilla... but maybe there is a way to pipe the query output
> into another filter before displaying?
> 
> At worse case, I still think having a new "Feature" severity would be  useful.
> 
> 
> 
> 
> _______________________________________________
> release-team mailing list
> release-team@kde.org
> https://mail.kde.org/mailman/listinfo/release-team
_______________________________________________
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team
[prev in list] [next in list] [prev in thread] [next in thread]