[Trac] Dates on versions and milestones

[Matthew Good]

On Fri, 2005-04-08 at 13:38 -0700, Robert Morris wrote:
> The “version time <name> <time>” allows one to assign a date to a
> version. I see no effect when assigning a date to a version on any of
> the (default provided) web pages for Trac.  What is the effect of
> putting a date on a version ? 

I'm not sure about this.  I don't use the date on versions myself, and I
haven't seen a place yet where they are used.


> What is the effect of putting a date on a milestone ?  Is do see
> _some_ effect in this case (in milestone view).  Is that the date the
> milestone is completed and you enter it when it gets reached ?

The milestone date can be used to set expected completion date, or the
actual completion date.  In 0.8.1 milestones are immediately considered
as completed if their date is reached.  In 0.9 this will be changed so
that they must actually be marked as completed, since you may have
milestones that go past the due date.  This value is displayed on the
roadmap as you noted.  The other place I know that it shows up is in the
iCal file, this will be used as the due date for the calendar tasks.

> Now conceptually I may have things backwards.  I have milestones names
> similiar to “Executive 1.7D Release”.  I also have a version named
> “1.7D”.  Does this run counter to the intent ?  Should milestones be
> “major functionality” and versions and the numbers assigned to
> releases of our software ?

Milestones and versions are generally going to relate directly to each
other.  The difference is that versions are used for existing releases,
and milestones represent future releases.  So the version field on a
ticket represents the version that the issue exists in.  The milestone
is the version where you expect to have the issue resolved.

So, when you make a release you will mark the milestone as complete, and
add a new version.  

-- 
Matthew Good <trac at matt-good.net>