Btw (aimed to Greg and anyone else) - never feel that the committers would be best to put it together. I've gotten Open Source projects out the door without being a committer simply by listing the things I/they thought they should work on on a wiki. It's a bit more of a pain without access to define versions in the issue tracker, but very doable.
For example - look at the list of JIRA issues and add your thoughts on whether it should or should not be in the next version. You'll be amazed (I hope) at how you can galvanize activity. Hen On Tue, Aug 9, 2011 at 4:05 PM, Phil Steitz <phil.ste...@gmail.com> wrote: > Thanks for the nudge. I'll bite. Of course anyone is welcome to > browse the open JIRA issues with 3.0 as fix version and add comments > :) > > Phil > > On Tue, Aug 9, 2011 at 2:59 PM, Greg Sterijevski <gsterijev...@gmail.com> > wrote: >> Does anyone have a list of showstopper bugs and features. If we want a 3.0 >> release soon, then perhaps some kind of a prioritized list would help us in >> the community concentrate some of our efforts? I was thinking that the >> individuals with commit privileges could put this together since they are >> probably most acutely aware of where things stand. Once that list is >> published, each of us in the community could commit to a task or two. >> >> >> -Greg >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
