#8 Procedure for new release preparation requires clarification

[Greg White]

Developers, esp Marty, have expressed that they would like the "EPICS Version 4 Core Module Development and Release Guide" (aka "Release Guide") [1] to be clarified in some respects.

1. Presently, the procedure described for tagging and branching, as illustrated in the
   the diagram in section "Mercurial Workflow for Versioning" [2] says that a branch need only
   be created for a tagged release if a change needs to be made to a file between the time that
   the repo is first tagged for that release, and the final packaging of the release.
   Marty wants the procedure to start with an explicit branch always, even before it's need.
   That is, one would tag the new release candidate, and immediately branch on that tag.

2. Marty would like the steps of release - what a programmer actually types - to be more
   explicit, rather than presented as a diagram [2].

3. Marty would like the explicit steps for Java and C++ to both be explicitly listed.

[1] http://epics-pvdata.sourceforge.net/release.html
[2] http://epics-pvdata.sourceforge.net/release.html#mercurial_workflow_for_versioning