From owner-svn-doc-all@FreeBSD.ORG Thu Mar 7 21:20:42 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id B1BCF292; Thu, 7 Mar 2013 21:20:42 +0000 (UTC) (envelope-from issyl0@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 764E6351; Thu, 7 Mar 2013 21:20:42 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r27LKguY014279; Thu, 7 Mar 2013 21:20:42 GMT (envelope-from issyl0@svn.freebsd.org) Received: (from issyl0@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r27LKgBO014278; Thu, 7 Mar 2013 21:20:42 GMT (envelope-from issyl0@svn.freebsd.org) Message-Id: <201303072120.r27LKgBO014278@svn.freebsd.org> From: Isabell Long Date: Thu, 7 Mar 2013 21:20:42 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r41126 - head/en_US.ISO8859-1/htdocs/news/status X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Mar 2013 21:20:42 -0000 Author: issyl0 Date: Thu Mar 7 21:20:41 2013 New Revision: 41126 URL: http://svnweb.freebsd.org/changeset/doc/41126 Log: Refresh the status report README to reflect the recent report production process. Hat: monthly Reviewed by: pgj Modified: head/en_US.ISO8859-1/htdocs/news/status/README Modified: head/en_US.ISO8859-1/htdocs/news/status/README ============================================================================== --- head/en_US.ISO8859-1/htdocs/news/status/README Thu Mar 7 18:36:50 2013 (r41125) +++ head/en_US.ISO8859-1/htdocs/news/status/README Thu Mar 7 21:20:41 2013 (r41126) @@ -25,7 +25,7 @@ Compiling status reports - best practice 4) Putting it all together: - Copy and paste all reports in a single .xml file and use tidy(1) to get - it well formatted. Usually 's without a description are missing + it well formatted. Usually s without a description are missing the closing "/>" which is the cause for most of the errors you will encounter. Sometimes other closing tags are missing. - Invoking tidy with the following options seems to cause the fewest @@ -44,7 +44,7 @@ Compiling status reports - best practice

Some more blabla ... -5) After the a couple iterations of the above, wrap the whole thing in a +5) After a couple of iterations of the above, wrap the whole thing in a report template: @@ -136,14 +136,11 @@ Report//EN" the html helps. Make sure you have an up-to-date doc tree. 6) Sending it out: - - Just prior to committing, build the html locally. - - Extract a text version: lynx -dump -nolist report.html > report.txt - - Prettify. - - Send out To: hackers, CC: current, stable. New email to: announce@ this - one needs to be approved. Find somebody who can do that before you - start. - - Commit. Also update the next due date in status.sgml and link to the - new report. + - Commit, hooking the report XML to the build but not linking to it + from anywhere. This gives time for other committers to review and + suggest minor changes. + - After a few days, collate and commit the changes. Also update the + next due date in status.xml and link to the new report. - Add a news entry to head/share/xml/news.xml. Template: June-October, 2006 Status Report @@ -152,5 +149,10 @@ Report//EN" href="&enbase;/news/status/report-2006-06-2006-10.html">now available with 49 entries.

+ - Extract a text version with the command + lynx -dump -nolist report.html > report.txt and prettify it. + - Send out To: hackers, CC: current, stable. New email to: announce@. + This needs to be approved, so find someone who can do that before you + start. 7) Repeat.