-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NXDL release 2020.1 #693
Comments
There's a checklist at the top of this issue. Perhaps that should become part of the release procedures on the wiki? We're at step 2 on that checklist. I'm looking at the work queue for the milestone and expecting that most remaining PRs will be complete by Thursday. Now that the release notes scripting is repaired (#735) but work remains to be merged, it's a good time to work the release process again with another R tag: v2020.1rc2. |
Each of the remaining PRs is waiting on one or more reviews. I sent messages to each reviewer yesterday with a request to review by COB Thursday. In one of them, I stated I want to release on Friday. Any unreviewed items will move to next milestone. |
Ok, I have completed the process for rc2. Please check all it okay. |
One addition is to link to the release notes from the tag comment. See https://github.com/nexusformat/definitions/releases/tag/v2018.5 for an example. Release notes look good. Updating the Change History needs to be added to the Release Procedure. The existing page refers to 2019.10 release that should be changed into v2020.1. The contents are hand-selected highlights from the release notes (since important items might be overlooked in the complete release notes). Fantastic! On Friday, you can do the final release of v2020.1 after completing the checklist above. Lessons learned
Anything else? |
One more lesson learned
Preparatory step
Get a GitHub personal access token, read only for access to repos,
milestones, pull requests, issues, ...
This is specific to the user for use on one workstation
…On Tue, Jan 28, 2020, 9:44 AM Peter Chang ***@***.***> wrote:
Ok, I have completed the process for rc2. Please check all it okay.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#693?email_source=notifications&email_token=AARMUMB5KH4BCQ4SM4BNTGDRABHFDA5CNFSM4JKYJSF2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKDZP4A#issuecomment-579311600>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AARMUMF63F6OFXTWWTEN62LRABHFDANCNFSM4JKYJSFQ>
.
|
On Fedora 31, need to install:
|
@PeterC-DLS we are ready now for release v2020.1 |
I just checked off items 2 & 3 in the check list above. |
Ok, I will proceed with release. |
All done up to and including step 13 so please check. I will be off-line so I will leave the last two steps to you. |
Thanks. Changed the release name to "v2020.1"
…On Fri, Jan 31, 2020, 7:34 AM Peter Chang ***@***.***> wrote:
All done so please check. I will be off-line so I will leave the mailing
list announcement to you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#693?email_source=notifications&email_token=AARMUMHIH6ELU3JLGR5UWNTRAQSH3A5CNFSM4JKYJSF2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKOVC3Q#issuecomment-580735342>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AARMUMBZYPGSMQYRCBBVZS3RAQSH3ANCNFSM4JKYJSFQ>
.
|
Follow the documented release procedure. Someone other than @prjemian should do this to test that procedure has been fully documented.
These steps:
Note: Any new issues will be assigned to next milestone after this code camp unless they are of immediate nature.
The text was updated successfully, but these errors were encountered: