[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: The future of the Subversion book

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: Thu, 6 Sep 2018 09:02:05 -0400

On 09/05/2018 04:10 PM, Daniel Shahaf wrote:
> Can we identify specific tasks that interested volunteers can pick up?
> Initial draft:
> - Respond to bug reports as they come in
> - Liaise with translators
> - Add content about <specific feature> from the <1.8/1.9/1.10/1.11> release
> - Bring the book up-to-speed with _all_ new features since 1.8 or 1.9 (?)
> - Go through the issue tracker backlog (is there one?)

Your list is a pretty complete one. I'd add, perhaps, "Maintain the
website" (which implies ensuring that the nightly builds are working).

Yes, there is an issue tracker:


I've used the issue tracker not merely for bug reports, but also for the
work of trying to update the text with respect to new features or
behaviors as new Subversion releases come out.

The milestones in the tracker are pretty straightforward: "en-1.8" is
something that needs to be fixed in the English version of the book that
covers Subversion 1.8, e.g. (You won't find "en-1.9" -- I'd planned to
skip the 1.9 version and go straight to 1.10.) I also have a "whenever"
milestone for stuff that can isn't tied to a specific version, and an
"unlikely" milestone for stuff that I was on the fence about even

I also used the project's wiki tool to track the high-level
documentation process:


If you cruise over some of the pages there, you'll see the exact process
that I (and formerly Ben, Fitz, and others) used to manage the
documentation of each new version of Subversion.

-- Mike
Received on 2018-09-06 15:02:29 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.