On 13/04/2012, at 11:56 AM, Szczepan Faber wrote: > On Fri, Apr 13, 2012 at 12:46 PM, Luke Daley <[email protected]> > wrote: > There are currently 73 issues scheduled to to be fixed in 1.0 according to > JIRA. > > http://issues.gradle.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+GRADLE+AND+fixVersion+%3D+%221.0%22+AND+resolution+%3D+Unresolved+ORDER+BY+due+ASC%2C+priority+DESC%2C+created+ASC&mode=hide > > I think we should adopt the policy of not applying fix for versions until we > start work on something and leave everything else unscheduled. > > I like it. It always feel like a dummy release step to push all jira tickets > forward with their 'fix for. Adam, what do you think? Do you use 'fix for' to > manage shortlists?
If so, we should maybe consider a different mechanism for shortlisting. -- Luke Daley Principal Engineer, Gradleware http://gradleware.com
