Merge pull request #669 from cylc/8.2.x

8.2.x

src/7-to-8/cheat-sheet.rst

@@ -260,6 +260,33 @@ Generate a visualisation for a workflow without running it:
 
        The web UI will have full graph vis. in a future release.
 
+Datetime Operations
+-------------------
+
+Datetime operations in task scripts:
+
+.. list-table::
+   :class: grid-table
+
+   * - **Cylc 7** & Rose 2019
+     - **Cylc 8** (Rose 2)
+   * - ::
+
+         rose date <point> --offset <offset>
+     - ::
+
+         isodatetime <point> --offset <offset>
+   * - ::
+
+         rose date -c
+         # equivalent to:
+         rose date "$CYLC_TASK_CYCLE_POINT"
+     - ::
+
+         isodatetime ref
+         # equivalent to:
+         isodatetime "$CYLC_TASK_CYCLE_POINT"
+
 Rose Stem
 ---------
 

src/user-guide/writing-workflows/scheduling.rst

@@ -599,10 +599,7 @@ The Environment Variable CYLC\_WORKFLOW\_INITIAL\_CYCLE\_POINT
 
 At start up the initial cycle point is passed to job environments
 as ``$CYLC_WORKFLOW_INITIAL_CYCLE_POINT`` and stored in the workflow
-database to persist across restarts. However it gets wiped out (set to
-``None``) by a :term:`warm start` (``cylc play --start-cycle-point`` or ``cylc
-play --start-task``) - which is essentially a restart that ignores prior state
-information.
+database to persist across restarts.
 
 The ``$CYLC_WORKFLOW_INITIAL_CYCLE_POINT`` variable allows tasks to
 check if they are running in the initial cycle point, when different behaviour