Menu
▾
▴
#170 issues with release process
After the release this morning, we identified a couple of issues that need resolving.
1) Step 3 re: analytics -- we need to resolve turning analytics off on 8.23 and on for 9.0, since we only want to be tracking the latter. This seems like it will only be an issue in the case of major releases.
2) Step 4 re: tagging -- need to emend the process to note that a tag should be added in Git.
3) Step 5 and 6 -- because the stylesheets are now housed in the GitHub repo, this step is unnecessary; however, the steps are required for the guidelines and schema uploads (step 6). These need to be revised to reflect that.
4) We are only uploading the html of the guidelines; this should be noted (under step 6).
5) Also, add note to ensure that the schema is the default download, not the guidelines (5.1).
6) Updated latest release wiki and email sections to include the new tag links on Git, etc.
I'll aim to take a stab at (most of) the later points here before next EDAG.
Also see comments in FR125, which still need addressing.
Last edit: BODARD Gabriel 2017-12-19
Addressed points 2, 3, 4, 5, and 6 above; made relevant changes to release process guidelines page on sourceforge. Didn't address FR125 yet.
Last edit: Scott DiGiulio 2017-12-31
Only remaining points are documenting analytics (I'll handle this week), and documenting the HTML choice FR125, which is now closed.
Last edit: Scott DiGiulio 2018-02-20
Added a couple of sentences addressing the html documentation, but I think the revisions to the release process should now be all set, unless there is something that stands out to others.