[Trac] Dates on versions and milestones

[Ronny Hanssen]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Beat me with a couple of seconds on tis one :)

Matthew Good wrote:
> 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.

That is true. I really didn't answer that in my reply neither. I haven't
used the version dates. Maybe it's a future thing to make it possible to
line up a release history?. Possibly with statistics for number of
bugs/feature requests pr release? There is also a possibility to add a
management interface for the workflow process of making a release.
Normally (in our projects) we work on fixing issues for the next
milestone. However, we often fix bugs or add features (intentionally or
not) for the next milestone(s). When releasing we are also releasing the
features/bugs already fixed that belongs to the next milestone. This is
true as long as all these fixes go into the trunk at least. Some of you
may use a branchpoint in those cases - I don't know). Well, we put all
changes in the trunk at least (as long as it is not a bugfix for a
previously released version - since that is put into that releases own
branch). Getting back to the issue I would further love to have a
process were the pm or similar declares a new version, and links this to
a tag in subversion. At the same time linking all tickets closed before
this to this version, preparing and suggesting release notes (as I
suggested earlier each ticket could have an optional field for release
notes). Unclosed tickets belonging to milestones included in this
release needs to be resolved. Normally either remove milestone marker or
move all unclosed tickets to the next milestone. Then this milestone
should be frozen. It shouldn't be possible to add tickets for it again,
why should one need to do so? That way it is also removed from the new
ticket form too, where they otherwise could confuse the author of the
ticket.


Regards,
- ------------------------------------------------------------------------
/*Ronny Hanssen*/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCVvZHMRRzQX3ma+kRAv2dAKClpSSki8uEKIpB4lYCY6wwlfDukACgrcFy
UcZFBNMPrRrtgNwCDpbHIxM=
=zty+
-----END PGP SIGNATURE-----