Turns out the obvious is not that obvious. State it: add the new status

report file to the Makefile, or Weird Things Will Happen.

en_US.ISO8859-1/htdocs/news/status/README

@@ -89,6 +89,14 @@ deadline  Follow up on missing reports
 
 5) Wrapping the whole thing in a report template:
 
+  - Create the new report with a filename of yyyy-mm-yyyy-mm.xml, where
+    the first mm is the starting month and the second mm is the ending
+    month.
+
+  - Add the new file to the XMLDOCS entries in the Makefile.
+
+  - Contents:
+
 <?xml version="1.0" encoding="iso-8859-1" ?>
 <!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for Status
 Report//EN"
@@ -169,12 +177,17 @@ Report//EN"
 
     <description>Miscellaneous</description>
   </category>
+
+  <project>
+    ...
+  </project>
+  ...
 </report>
 
  - Categories are subject to change obviously.  They come out in the order
    as stated in the report.  After another round of tidy(1) try to balance
    the categories.  Put things where they belong best, retire categories
-   that don't fill up, etc.  Adding it to your local build and looking at
+   that do not fill up, etc.  Adding it to your local build and looking at
    the html helps.  Make sure you have an up-to-date doc tree.
 
  - theraven may be poked for composing a nice introduction for the reports.