On Wed, Dec 19, 2012 at 11:39 AM, Philip Martin
>>> I don't mean milestones of 'unscheduled', 'nonblocking', of 'blue-sky',
> Do those milestones have an agreed meaning? What is the difference?
My understanding of unscheduled and nonblocking as is per
When an issue is first filed, it automatically goes in the "---"
target milestone, which indicates that the issue has not yet been
processed. A developer will examine it and maybe talk to other
developers, then estimate the bug's severity, the effort required to
fix it, and schedule it in a numbered milestone, for example 1.1. (Or
they may put it the unscheduled or nonblocking milestone, if they
consider it tolerable for all currently planned releases.)
An issue filed in unscheduled might still get fixed soon, if some
committer decides they want it done. Putting it in unscheduled merely
means it hasn't been scheduled for any particular release yet. The
nonblocking milestone, on the other hand, means that we do not
anticipate ever scheduling the issue for a particular release. This
also does not mean the issue will never be fixed; it merely means that
we don't plan to block any release on it.
Not sure about 'blue-sky'. There are only 16 open issues with this
milestone. I always took it mean something along the lines of 'not
going to happen before 2.0 or without a massive amount of work for
limited gain', but I don't know that there is any official definition.
> Certified & Supported Apache Subversion Downloads:
Paul T. Burba
CollabNet, Inc. -- www.collab.net -- Enterprise Cloud Development
Received on 2012-12-19 17:48:35 CET