Merged in branch/iola/milestones, which provides datatracker support for management of WG milestones.

 - Legacy-Id: 5739

Author: levkowetz

INSTALL

@@ -121,6 +121,17 @@ usual, with re-pointing the symlink and restarting apache.
 Additional Version-Specific Instructions
 ========================================
 
+Version 4.46
+------------
+
+Before you run step 3 (migration) of the general instructions, please run some specific
+initial migrations with the a --fake argument:
+
+      cd $releasenumber
+      PYTHONPATH=$PWD ietf/manage.py migrate group 0001 --fake
+      cd ..
+
+
 Version 4.42
 ------------
 

changelog

@@ -1,3 +1,14 @@
+ietfdb (4.46) ietf; urgency=medium
+
+    This is a major feature release, which introduces datatracker support
+    for milestone management.  WG Chairs will, if they are logged in, see
+    an 'Add or edit milestones' button on the WG's Charter page in the
+    datatracker, just below the charter text, and Area Directors and
+    Secretariat staff will see a new link 'Milestones' in the left-hand
+    menu-bar, leading to a page which lists Milestones Needing Review.
+
+ -- Henrik Levkowetz <henrik@levkowetz.com>  14 May 2013 21:50:09 +0200
+
 ietfdb (4.45) ietf; urgency=medium
 
   This release contains bugfixes and some minor features.

ietf/__init__.py

@@ -1,4 +1,4 @@
-# -*- coding: utf-8 -*-
+# -*- coding: utf-8-no-bom -*-
 # Copyright The IETF Trust 2007, All Rights Reserved
 
 __version__ = "4.46-dev"

ietf/bin/send-milestone-reminders

@@ -0,0 +1,45 @@
+#!/usr/bin/env python
+#
+# This script will send various milestone reminders. It's supposed to
+# be run daily, and will then send reminders weekly/monthly as
+# appropriate.
+
+import datetime, os
+import syslog
+
+from ietf import settings
+from django.core import management
+management.setup_environ(settings)
+
+syslog.openlog(os.path.basename(__file__), syslog.LOG_PID, syslog.LOG_LOCAL0)
+
+from ietf.wginfo.mails import *
+
+today = datetime.date.today()
+
+MONDAY = 1
+FIRST_DAY_OF_MONTH = 1
+
+if today.isoweekday() == MONDAY:
+    # send milestone review reminders - ideally we'd keep track of
+    # exactly when we sent one last time for a group, but it's a bit
+    # complicated because people can change the milestones in the mean
+    # time, so dodge all of this by simply sending once a week only
+    for g in groups_with_milestones_needing_review():
+        mail_sent = email_milestone_review_reminder(g, grace_period=7)
+        if mail_sent:
+            syslog.syslog("Sent milestone review reminder for %s %s" % (g.acronym, g.type.name))
+
+
+early_warning_days = 30
+
+# send any milestones due reminders
+for g in groups_needing_milestones_due_reminder(early_warning_days):
+    email_milestones_due(g, early_warning_days)
+    syslog.syslog("Sent milestones due reminder for %s %s" % (g.acronym, g.type.name))
+
+if today.day == FIRST_DAY_OF_MONTH:
+    # send milestone overdue reminders - once a month
+    for g in groups_needing_milestones_overdue_reminder(grace_period=30):
+        email_milestones_overdue(g)
+        syslog.syslog("Sent milestones overdue reminder for %s %s" % (g.acronym, g.type.name))

ietf/doc/models.py

@@ -465,6 +465,7 @@ class DocReminder(models.Model):
     # WG events
     ("changed_group", "Changed group"),
     ("changed_protocol_writeup", "Changed protocol writeup"),
+    ("changed_charter_milestone", "Changed charter milestone"),
 
     # charter events
     ("initial_review", "Set initial review time"),

ietf/group/admin.py

@@ -116,9 +116,9 @@ class GroupHistoryAdmin(admin.ModelAdmin):
 admin.site.register(GroupHistory, GroupHistoryAdmin)
 
 class GroupMilestoneAdmin(admin.ModelAdmin):
-    list_display = ["group", "desc", "expected_due_date", "time"]
-    search_fields = ["group__name", "group__acronym", "desc"]
-    raw_id_fields = ["group"]
+    list_display = ["group", "desc", "due", "resolved", "time"]
+    search_fields = ["group__name", "group__acronym", "desc", "resolved"]
+    raw_id_fields = ["group", "docs"]
 
 admin.site.register(GroupMilestone, GroupMilestoneAdmin)