Provide Possibility to 'freeze' a Milestone

[ilias@…]

It should be possibly to flag a milestone as 'freezed', thus no new tickets can be filed.

see #3730 for an example-conflict.

[cmlenz]

This is a workflow thing, and IMHO not something generic enough to warrant complicating to the Trac core code and UI.

[anonymous]

Don't get annoyed by him: I found something here:
​http://en.wikipedia.org/wiki/Ilias_Lazaridis

"Ilias Lazaridis is an Internet personality who frequents programming-related discussion groups and mailing lists. Lazaridis posts to various groups and lists, typically presenting himself in the role of an analyst or "auditor" from "Lazaridis System Design" who is evaluating a language or tool for use on an unspecified project. Despite this innocent beginning, threads begun by Lazaridis often devolve into flame wars, leading many to suspect he is an internet troll.

The Lazaridis System Design website claims to sell consulting and auditing services, and Lazaridis's posts often contain multiple links that site. On occasion, Lazaridis mentions that he will offer a "reduced rate" for analysis of open-source projects. The combination of repeated linking to his own site and mentions of his rates for analysis have led some to suspect he may be a spammer.
Lazaridis is known to have posted to the following lists:

• apache
  
• archetypes-devel
  
• caml-list
  
• comp.lang.java.softwaretools
  
• comp.lang.lisp
  
• comp.lang.python
  
• comp.lang.ruby
  
• comp.lang.tcl
  
• comp.python.pudge.general
  
• django-developers
  
• schevo-devel (Use cache links as this list archive was recently moved.)
  
• turbogears
  

Lazaridis has been banned from several lists, including but not limited to the following:

• django-developers
  
• schevo-devel"

[mgood]

Replying to anonymous:

Don't get annoyed by him: I found something here:
​http://en.wikipedia.org/wiki/Ilias_Lazaridis

We are aware of that. Please try not to post off-topic content on the tickets. Use the MailingList, IrcChannel, or if you need to send a private mail most of the TracTeam has email addresses listed.

[kirean@…]

I'm in a project where we've implemented this by using an new column: 'frozen' in the milestone table.

We've combined this with a pre-commit check that won't allow ny commits vs. a milestone unless it's a defect(bug). Of course the world isn't always perfect so there are situations where we need to allow this and we solve it either by unfreezing the milestone or by a special "tag" sent in the commit message.

The logic for this is thus not in trac and maybe it should be better to have it all in Trac..

Anyway, if anyone would find this useful I can upload/e-mail a patch for it.

[cboos]

I don't see how we can implement this without changing the milestone table, and in the absence of a critical need, I'd like to keep the 0.11 database model the same as the one of 0.10.

Therefore I think we can post-pone this to 0.12:

• I already plan changes for the Milestone implementation that would make such feature trivial to add (see GenericTrac)
• A bit less trivial would be to consider this request as an example of wanting customizable workflow for milestones, in a similar way we have it now for tickets (see WorkFlow). Here, this would be:
  • freeze = new -> frozen
  • unfreeze = frozen -> new
  • close = new, frozen -> closed

[ilias@…]

A possible solution without database-modification:

provide a ini-file parameter like "mileston-freeze-period-in-days"

The trac code (either server or even better the UI) could do this check:

if (date.now + ini.freeze_period > milestone.due_date):

# do not allow assignment of ticket to this milestone

[osimons]

"...thus no new tickets can be filed" is basically the discussion on #1440 that is now fixed for 0.11.

I'm closing this one as a duplicate.

[ilias@…]

Replying to osimons:

"...thus no new tickets can be filed" is basically the discussion on #1440 that is now fixed for 0.11.

I'm closing this one as a duplicate.

This is not a duplicate, but a similar issue.

"thus no new tickets can be filed" against the freezed(!) milestone.

As cboos mentioned above, it affects essentially the introduction of the status "freezed" for milestones.

Reopen (as it's not a duplicate)

[cboos]

Well, in reference to comment:6, we can eventually keep this ticket opened as an example for a need of a "custom workflow" for milestones.

[kirean@…]

Replying to cboos:

Well, in reference to comment:6, we can eventually keep this ticket opened as an example for a need of a "custom workflow" for milestones.

I agree. Something like what cboos wrote in comment:6 would be nice to have. I think osimons was a little too fast closing this one.

[cboos]

Milestone 2.0 deleted

[Erik Andersson <kirean@…>]

Sweet!