[svnbook] r3857 committed - Similarly tweak SvnBook17Status per r3856.
svnbook at googlecode.com
svnbook at googlecode.com
Wed Jun 29 14:16:49 CDT 2011
Revision: 3857
Author: cmpilato at gmail.com
Date: Wed Jun 29 12:16:20 2011
Log: Similarly tweak SvnBook17Status per r3856.
http://code.google.com/p/svnbook/source/detail?r=3857
Modified:
/wiki/SvnBook17Status.wiki
=======================================
--- /wiki/SvnBook17Status.wiki Mon Jun 27 12:23:23 2011
+++ /wiki/SvnBook17Status.wiki Wed Jun 29 12:16:20 2011
@@ -4,9 +4,17 @@
There are no known major reorganizations required to update svnbook to
cover Subversion 1.7. However, the replacement of the old working copy
library with the new WC-NG in Subversion 1.7 could necessitate fairly
substantial section rewrites. C. Michael Pilato plans to take the
following multi-step approach to the task:
-== Step 1: Read-thru ==
-
-Full read-thru of the book, cover-to-cover, updating each of the following
chapters for accuracy:
+== Step 1: Review Release Notes ==
+
+The Subversion project's
[http://subversion.apache.org/docs/release-notes/1.7.html release notes]
are generally pretty good at pointing out subtle (and major) behavior
changes. Check these for stuff missed elsewhere, and file appropriately
milestones issues for changes that need to be made.
+
+== Step 2: Review Issues ==
+
+Review outstanding
[http://code.google.com/p/svnbook/issues/list?q=label:Milestone-en-1.7
issues] marked for closure in this version.
+
+== Step 3: Read-thru ==
+
+Full read-thru of the book, cover-to-cover, updating each of the following
chapters for accuracy and coherancy:
* Preface
* Chapter 1. Fundamental Concepts
@@ -23,10 +31,6 @@
* Chapter C. WebDAV and Autoversioning
* Chapter D. Copyright
-== Step 2: Review Issues ==
-
-Review outstanding
[http://code.google.com/p/svnbook/issues/list?q=label:Milestone-en-1.7
issues] marked for closure in this version.
-
-== Step 3: Update Index ==
+== Step 4: Update Index ==
We've never had a real index in the open source version of the book, and
it would be great to solve this problem. This shouldn't be considered a
showstopper, though.
More information about the svnbook-dev
mailing list