You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We haven't been keeping up with the release notes for pyspedas -- on our github repo it only looks like some of the very early releases have been documented. We should bring this up to date by adding tags for each release, and compiling release notes from the commit history. We might also want to add release notes somewhere on our readthedocs pages.
Going forward, we should ensure that updating the release notes is part of our release workflow.
We're up to date now. I think I made a few mistakes in the tagging -- I think I was tagging the previous commit rather than the one I intended to tag in a few places. To attach a tag to the previous commit:
or use the PyCharm to do the push, and make sure that the "push tags" option is checked in the confirmation dialog.
To make the release notes on the Github repo, go to the pyspedas repo page, and click on "Releases" in the right column. There will be a "Draft a new release" button. Click that, select a tag from the dropdown, name it "PySPEDAS vX.Y.Z",. and click on "Generate Release Notes" which gives you the commit log messages between the previous tag and the new tag.
We haven't been keeping up with the release notes for pyspedas -- on our github repo it only looks like some of the very early releases have been documented. We should bring this up to date by adding tags for each release, and compiling release notes from the commit history. We might also want to add release notes somewhere on our readthedocs pages.
Going forward, we should ensure that updating the release notes is part of our release workflow.
See also: #1032 and #1031
The text was updated successfully, but these errors were encountered: