<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.10.3">
</HEAD>
<BODY>
On Wed, 2006-09-27 at 12:52 +0200, Adrian Brock wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">On Mon, 2006-09-25 at 10:40 -0600, Andrig T Miller wrote:</FONT>
<FONT COLOR="#000000">> The idea behind this is to keep releases from filling with</FONT>
<FONT COLOR="#000000">> everything, and them not getting reviewed. When things are directly</FONT>
<FONT COLOR="#000000">> assigned to releases, everyone just assumes it should be done, and</FONT>
<FONT COLOR="#000000">> there is no review. By having them initially unscheduled, and</FONT>
<FONT COLOR="#000000">> instituting a mandatory review, we can intelligently assign them to</FONT>
<FONT COLOR="#000000">> the proper release with the proper priority. They shouldn't remain in</FONT>
<FONT COLOR="#000000">> unscheduled for any length of time.</FONT>
<FONT COLOR="#000000">> </FONT>
<FONT COLOR="#000000">> Before we did this, releases just grow in scope unchecked, and we</FONT>
<FONT COLOR="#000000">> cannot continue to do that.</FONT>
<FONT COLOR="#000000">You can't fix the problem of bugs not getting reviewed by</FONT>
<FONT COLOR="#000000">hiding them under the rug. :-)</FONT>
</PRE>
</BLOCKQUOTE>
<BR>
Having them unscheduled doesn't hid them under any rug. They are just as visible in JIRA.
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">Assigning to a release, forces somebody to remove</FONT>
<FONT COLOR="#000000">them from that release. So they are least looked at.</FONT>
</PRE>
</BLOCKQUOTE>
<BR>
All it really does is force someone to go into JIRA and change the fix version, not to actually evaluate the issue.<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">Where this failed before, is that they had no assignees.</FONT>
<FONT COLOR="#000000">So Dimitris just bumped to the next release without</FONT>
<FONT COLOR="#000000">pinging the assignee to tell them to</FONT>
<FONT COLOR="#000000">"to pull his finger out ..." :-)</FONT>
<FONT COLOR="#000000">If don't want to assign a bug to release, </FONT>
<FONT COLOR="#000000">e.g. it is too complicated to fix in the near future</FONT>
<FONT COLOR="#000000">there is a "No Release" dummy version.</FONT>
<FONT COLOR="#000000">But doing this, will probably lead to them</FONT>
<FONT COLOR="#000000">getting forgotten about!</FONT>
</PRE>
</BLOCKQUOTE>
<BR>
To really solve this, is we need a formal review process. It doesn't matter whether something is assigned to a release or not. We have to have formal, mandatory review as a team.<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<PRE>
</PRE>
</BLOCKQUOTE>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
Andrig (Andy) Miller<BR>
VP, Engineering<BR>
JBoss, a division of Red Hat
</TD>
</TR>
</TABLE>
</BODY>
</HTML>