Skip to content

Commit

Permalink
SSC checklist : update when dev -> master PR is merge
Browse files Browse the repository at this point in the history
  • Loading branch information
kbjarkefur authored Oct 22, 2018
1 parent e4ee5f4 commit 48d0fd4
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions src/checklist-submitting-SSC.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,10 +10,10 @@
- [ ] 6. **Make sure that there is no conflicts in the pull request you just created** - Make sure to include any edits this step requires you to do in the version you are sending to SSC. Do not merge yet.
- [ ] 7. **Copy files to archive folder** - Make a folder with named after the new version number in the archive folder Dropbox\DIME Analytics\Data Coordinator\ietoolkit\ietoolkit archive\ and copy all ado-files and help files for all *ietoolkit* commands there.
- [ ] 8. **Create a .zip file** - Create a .zip file with all ado-files and help files in the folder you just created in the archive folder. Then remove all files but the .zip file from the archive folder.
- [ ] 9. **Email Prof. Baum** - Email the .zip file to **[email protected]**. If any commands are added or deleted, make note of that in the email.
- [ ] 10. **Draft release note** - Go to the [release notes](https://github.com/worldbank/ietoolkit/releases) and draft a new release note for the new version. Follow the format from previous releases with links to [issues](https://github.com/worldbank/ietoolkit/issues) solved.
- [ ] 11. **Wait for publication confirmation** - Do not proceed pass this step until Prof. Baum has confirmed that the new version is uploaded to the servers.
- [ ] 12. **Merge the pull request** - Merge the pull request for this new version. It should not have any conflicts, so just merge it. Remeber to delete the *develop* branch and create a new *develop* branch from the most recent version of the *master* branch.
- [ ] 9. **Merge the pull request** - Merge the pull request for this new version. It should not have any conflicts, so just merge it. Remeber to delete the *develop* branch and create a new *develop* branch from the most recent version of the *master* branch.
- [ ] 10. **Email Prof. Baum** - Email the .zip file to **[email protected]**. If any commands are added or deleted, make note of that in the email.
- [ ] 11. **Draft release note** - Go to the [release notes](https://github.com/worldbank/ietoolkit/releases) and draft a new release note for the new version. Follow the format from previous releases with links to [issues](https://github.com/worldbank/ietoolkit/issues) solved.
- [ ] 12. **Wait for publication confirmation** - Do not proceed pass this step until Prof. Baum has confirmed that the new version is uploaded to the servers.
- [ ] 13. **Publish release note** - Once the new version is up on SSC, publish the release note.
- [ ] 14. **Close issues** - When the new version is up, close all the [issues](https://github.com/worldbank/ietoolkit/issues) that was solved in the new version.
- [ ] 15. **Send announce email** - If it is a major release (new commands or significant updates to existing commands), send an email to DIME Team to announce the new version.
Expand Down

0 comments on commit 48d0fd4

Please sign in to comment.