#125 Updates needed to release process

[BODARD Gabriel]

Issues identified during release 8.23 that need to be incorporated in the release process for future releases.

1. Note that release technician needs to be given SF creds well in advance (and confirm which creds needed) of Day 15, sine creds may take hours to propagate. (First part noted in ReleaseProc)
2. Did we decide that the download package for the guidelines contains only the HTML of the GLs? If so, perhaps add a README in this folder, and change the ReleaseProc accordingly.
3. In file download area, note that only one download package (GLs, Schema or Stylesheets) can be set as the defaut EpiDoc download. We should decide which one is the most appropriate, and note accordingly in the ReleaseProc. (At the moment it is whichever one we happen to update settings on last.) Or we need to change the way we upload to file release area, and create a single package of all three components to download?
4. For clarity, I suggest we remove all "how to" sections of the ReleaseProc into separate pages/READMEs, and link out to them. This page should be a checklist, rather than guidelines for advanced and beginner users alike.
5. As per [bugs:#155] we should also add instructions for creating chained EpiDoc ODD to the release proc.

[BODARD Gabriel]

2. Let's document the reasoning behind the decision this time.
3. GB will survey Markup to decide what the default should be and report back.
4. Plus visual highlight for items that have to be done by GB/HC/TE (upload to Stoa)
5. GB+HC put heads together and document a couple of methods

[Scott DiGiulio]

I think points 1, 2, and 3 are (at least partially) addressed by the changes made to address bugs:#170; still need to document the choice for 2.