Yes, if there's no one assigned to a task, it's fair game. Or if the task is assigned but has been stale for a while.
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=12310734&status=1&status=3&status=4&fixfor=12314810&fixfor=12315179&fixfor=12314884&fixfor=12313152&fixfor=12313707&fixfor=12313418&fixfor=12313289&fixfor=12313159&fixfor=12312952&fixfor=12312910&fixfor=12312928&assigneeSelect=unassigned&sorter/field=issuekey&sorter/order=DESC&sorter/field=priority&sorter/order=DESC Beyond that, any of your personal pet peeve, issues, itches, wishes, dreams... bring it on! alaex On Tue, Jul 13, 2010 at 7:49 AM, Shane Witbeck <[email protected]>wrote: > I've added another patch for > https://issues.apache.org/jira/browse/BUILDR-466 > > Is there a good way to determine what issues need attention? For example, > if > there's no one assigned to a task? Most of the issues I see seem to be > either in progress already, waiting to have a patch applied, or cannot > reproduce. > > I'd like to contribute more but also don't want to duplicate effort. > > Thanks, > Shane > > On Fri, Jul 9, 2010 at 12:53 PM, Antoine Toulme <[email protected] > >wrote: > > > We have 9 issues fixed. > > > > We have failures in the trunk: > > BUILDR-144 specs don't pass on JRuby. I filed JRUBY-4927 and am following > > up > > with the JRuby team on that. > > BUILDR-317 don't pass on MRI. There is a bug with Java constructors for > RJB > > or something similar. I will follow up on that. > > > > Jira indicates 16 more issues for 1.4.2: > > https://issues.apache.org/jira/browse/BUILDR/fixforversion/12315179 > > > > There is a lot of exciting work to do, so please grab bugs if you want to > > volunteer for them. If something is out of the 1.4.2 scope, and you'd > like > > to see it included, please send a message to the dev list and make a case > > for it. > > > > Cheers! > > > > Antoine > > > > > > -- > -Shane >
