It is possible to do (but a pain) by setting up the smaller tasks as sub-tasks on major bugs and then only setting the version for the major bugs.
I don't like doing that so much since it is fairly intricate. If you have a marker for majorness, you can probably build a custom report to do the job as well. On Fri, Jan 21, 2011 at 1:34 AM, Lars George <[email protected]> wrote: > +1 on dropping and I like the JIRA based roadmap, but it is somewhat > hard to read for others. Would there be a way to use super/uber issues > for the main goals and then add the others underneath? I do not think > the priority etc. is good for that as a bug fix being a blocker rather > falls under a "Misc Stability Fixes" etc. I know, sounds like a purely > bureaucratic request and may be overkill and also not what JIRA is > for. I am just asking as it would be nice to condense fixes into the > major goals for a release. > > On Fri, Jan 21, 2011 at 6:42 AM, Jonathan Gray <[email protected]> wrote: > > +1 on dropping 0.20.7 > > > >> -----Original Message----- > >> From: Andrew Purtell [mailto:[email protected]] > >> Sent: Thursday, January 20, 2011 10:14 PM > >> To: [email protected] > >> Subject: Re: HBase roadmaps > >> > >> I didn't know this view existed in jira. Nice. > >> > >> I think we can drop 0.20.7. Would anyone recommend its use? > >> > >> - Andy > >> > >> > >> > From: Stack <[email protected]> > >> > Subject: Re: HBase roadmaps > >> > To: [email protected] > >> > Date: Thursday, January 20, 2011, 9:55 PM So I edited up the 0.92 > >> > description. RoadMap looks like this now: > >> > > >> > https://issues.apache.org/jira/browse/HBASE?report=com.atlassian.jira > . > >> > plugin.system.project:roadmap-panel > >> > > >> > Its showing 0.20.7, then 0.90.1, then 0.92.0. You think that right? > >> > (I wonder if we are going to do a 0.20.7 -- maybe I should drop it?). > >> > >> > >> > >> > > >
