Move tickets from 0.6.x to here once you're sure you're going to fix them for the next release.
There can be minor enhancements here, but nevertheless we should dedicate this branch to fixing defects still present in 0.6.0.
Pool of tickets which are going to be implemented in one of the next minor releases for version 0.6
The not applicable milestone is a special milestone which is currently used to distinguish between tickets that have not yet been triaged (see TicketTriage) and those who have, but for which there's no "real" milestone deemed to be adequate.
This can happen in the following situations:
- for bugs concerning a 3rd party software (like Subversion), which are occurring frequently enough to be kept opened and documented here, until an external resolution is found (when closing such tickets as wontfix is not really an option, as this would discourage people for following the progress, reporting the workarounds, etc.)
- for tasks to be done on t.e.o (usually in association with the project component)
Tickets that concern sgvizler but are not part of the schedule are assigned to unscheduled.
This milestone collects the tickets which need a deeper look in order to be triaged.
All tickets that are neither invalid nor rejected, but simply not part of the road map defined by the developers.
If a ticket ends up here, it means it probably will never get done unless someone steps up to champion it, becomes an active member of the team and implements it.