[releng/mcatanzaro/freeze-dates] Print the date a freeze begins

[Michael Catanzaro <mcatanzaro src gnome org>]

commit e2f4bd892669d4ac8cc445ba69c30f1ba77c224c
Author: Michael Catanzaro <mcatanzaro redhat com>
Date:   Thu Feb 24 14:53:00 2022 -0600

    Print the date a freeze begins
    
    Otherwise, it looks like string freeze is beginning the day the mail is
    sent, when in actuality it doesn't begin until three days later.

 tools/schedule/libschedule.py | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)
---
diff --git a/tools/schedule/libschedule.py b/tools/schedule/libschedule.py
index 11a8cadf..5d8ec166 100755
--- a/tools/schedule/libschedule.py
+++ b/tools/schedule/libschedule.py
@@ -80,21 +80,21 @@ update of the GNOME runtime.""",
             'description_template': {
                 'string-announcement': 'String Change Announcement Period',
                 'ui-announcement': 'UI Change Announcement Period',
-                'api': """No API or ABI changes should be made in the platform libraries. For instance, no 
new functions, no changed function signatures or struct fields.
+                'api': """API freeze begins on $date at 23:59 UTC. No API or ABI changes should be made in 
the platform libraries. For instance, no new functions, no changed function signatures or struct fields.
 
 This provides a stable development platform for the rest of the schedule.
 
 There should usually be a "Slushy" API/ABI Freeze before the Hard API/ABI Freeze, to encourage developers to 
think about API problems while they have a chance to correct them.
 
 API freeze is not required for non-platform libraries, but is recommended.""",
-                'feature': """Desktop and platform release module additions are finalised, major feature 
additions are listed. No new modules or features will be accepted for this release period. "Feature" should 
be interpreted as "Functionality" or "Ability". Bug fixes of existing features are not affected.
+                'feature': """Feature freeze begins on $date at 23:59 UTC. Desktop and platform release 
module additions are finalized, major feature additions are listed. No new modules or features will be 
accepted for this release period. "Feature" should be interpreted as "Functionality" or "Ability". Bug fixes 
of existing features are not affected.
 
 This allows developers to concentrate on refining the new features instead of adding yet more 
functionality.""",
-                'ui': """No major UI changes may be made without confirmation from the release team. Small 
fixes do not require permission.""",
-                'string': """No string changes may be made without confirmation from the i18n team.
+                'ui': """UI freeze begins on $date at 23:59 UTC. No major UI changes may be made without 
confirmation from the release team. Small fixes do not require permission.""",
+                'string': """String freeze begins on $date at 23:59 UTC. No string changes may be made 
without confirmation from the i18n team.
 
 From this point, developers can concentrate on stability and bugfixing. Translators can work without 
worrying that the original English strings will change, and documentation writers can take accurate 
screenshots. For explanation of the string freeze, and to see which kind of changes are not covered by freeze 
rules, check https://wiki.gnome.org/TranslationProject/HandlingStringFreezes. """,
-                'hard-code': """This is a late freeze to avoids sudden last-minute accidents which could 
risk the stability that should have been reached at this point. No source code changes are allowed without 
approval from the release team, but translation and documentation should continue. Simple build fixes are, of 
course, allowed without asking. """,
+                'hard-code': """Hard code freeze begins on $date at 23:59 UTC. This is a late freeze to 
avoids sudden last-minute accidents which could risk the stability that should have been reached at this 
point. No source code changes are allowed without approval from the release team, but translation and 
documentation should continue. Simple build fixes are, of course, allowed without asking. """,
                 'hard-code-end': """Hard Code Freeze ends, but other freezes remain in effect for the stable 
branch."""
             },
         },