On 13/04/2012, at 8:46 PM, Luke Daley 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.
This is the policy. Sometimes people like to fill in the fix-for field when they create the issue. Plus we haven't garbage collected all the old fix-for 1.0 values yet. This will happen at some point soon. -- Adam Murdoch Gradle Co-founder http://www.gradle.org VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com
