Skip to content
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

Discussion on next release #84

Closed
frankinspace opened this issue Sep 13, 2024 · 5 comments · Fixed by #86
Closed

Discussion on next release #84

frankinspace opened this issue Sep 13, 2024 · 5 comments · Fixed by #86
Labels
question Further information is requested

Comments

@frankinspace
Copy link
Collaborator

There are a number of changes that have been completed:

https://github.com/nasa/python_cmr/blob/develop/CHANGELOG.md#unreleased

Suggestion is to create a release containing all of these changes. I think it makes sense for the next release to be a minor release as 0.13.0.

@nasa/python_cmr any objections?

@frankinspace frankinspace added the question Further information is requested label Sep 13, 2024
@chuckwondo
Copy link
Collaborator

Works for me! Perhaps just tweak the very minor markdown issue at the end of the last item in the unreleased list in the changelog.

@frankinspace frankinspace linked a pull request Sep 13, 2024 that will close this issue
@frankinspace
Copy link
Collaborator Author

@chuckwondo @briannapagan FYI I started a release wiki page to outline the steps necessary to publish a new release https://github.com/nasa/python_cmr/wiki/Release-Process. Please review it when you get a chance. I'd like to have one of you run the release process next time if possible

@chuckwondo
Copy link
Collaborator

@chuckwondo @briannapagan FYI I started a release wiki page to outline the steps necessary to publish a new release https://github.com/nasa/python_cmr/wiki/Release-Process. Please review it when you get a chance. I'd like to have one of you run the release process next time if possible

Great!

In the section "Step 2: Prepare release branch" should the first step (prior to the current first step) be "Pull the latest revision from the develop branch"?

@frankinspace
Copy link
Collaborator Author

@chuckwondo updated

@chuckwondo
Copy link
Collaborator

The release process looks good. Next time, when either @briannapagan or I run through the process, we can make further adjustments to the doc, if we find anything else requiring clarification. Thanks again!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants