Edgewall Software

Milestone not applicable

admin/console

1 / 1

admin/web

2 / 2

contrib

0 / 9

database backend

0 / 2

general

18 / 22

i18n

1 / 1

plugin/mercurial

16 / 16

plugin/spamfilter

13 / 13

project

18 / 19

report system

0 / 1

ticket system

0 / 1

version control

3 / 5

version control/log view

1 / 1

web frontend

1 / 2

web frontend/mod_python

1 / 1

wiki system

2 / 2

The not applicable milestone is a special milestone which is currently used to distinguish between tickets that have not yet been triaged (see TracTicketTriage) 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 Trac but are not part of the schedule are assigned to unscheduled.

Note: See TracRoadmap for help on using the roadmap.