adding doc with release instructions #444
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Can you create a new toc under a |
SaOgaz
force-pushed
the
release_notes
branch
from
483ffb6
to
e3f1e7e
Compare
|
Zenodo errors? |
eteq
approved these changes
Feb 28, 2019
There was a problem hiding this comment.
I added a couple of additions @SaOgaz - see the two commits above (the were a bit awkward to "suggest" due to the need to update the later numbers...). Also one suggestion (which actually does fit in one line).
Otherwise looks fine to me, though. We could add more but I think it's better to get this in and then update it later if need be.
Co-Authored-By: SaOgaz <ogaz@stsci.edu>
|
LGTM, thanks for the edits @eteq! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pretty brief at the moment... can always be filled out more later.