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

Release dcw 2.0.2 #39

Closed
14 tasks done
maxrjones opened this issue Dec 12, 2021 · 13 comments
Closed
14 tasks done

Release dcw 2.0.2 #39

maxrjones opened this issue Dec 12, 2021 · 13 comments

Comments

@maxrjones
Copy link
Member

maxrjones commented Dec 12, 2021

Version: 2.0.2

Scheduled date: XXX XX, 20XX

Before release:

  • Check the changelog.
  • Check the settings in config.mk.
    • GMT_VERSION sets the correct minimum required GMT version.
    • DCW_VERSION sets the correct version of DCW to be released.
    • DCW_DATE sets the correct release date.
  • Run make spotless to clear out any old distribution files.
  • Run make all to make the dcw-gmt.nc file, create the tarball and zipfile, compute the MD5 checksum of the tarball, and create the dcw figure.
  • Run place-gmt to place the tarball on the gmt ftp (@meghanrjones or @Pwessel).
  • Run place-dcw to place the zip file on the dcw ftp and website (@Pwessel).
  • Create a new GitHub release.
    • Upload the tarbell.
    • Add a description to the release.
    • Add the MD5 checksum to the release notes.
  • Run update-dataserver to update the files on the GMT server using the GitHub release (@Pwessel or @meghanrjones).
@maxrjones
Copy link
Member Author

@Esteban82 and @PaulWessel, what do you think for the timing on releasing the 2.0.2 patch release? Are there any remaining issues to be tackled first (e.g., #38)?

@PaulWessel
Copy link
Member

@Esteban82 can merge #38 I think, should have no visual effect on results.

@Esteban82
Copy link
Member

@Esteban82 and @PaulWessel, what do you think for the timing on releasing the 2.0.2 patch release? Are there any remaining issues to be tackled first (e.g., #38)?

No. The only thing to be fixed was the Russian islands (already done).
I think it is better to make this release before #38. As Paul said it has no visual improvement and the release will have the same size. We later can, with no rush, see #38.

@Esteban82
Copy link
Member

I think we can go on with this. The changelog is updated.

@PaulWessel
Copy link
Member

OK, I will work through this later today. Have 3 zooms on the agenda and family visitors...

@PaulWessel
Copy link
Member

Working through the release steps now.

@PaulWessel
Copy link
Member

Hi @meghanrjones and @Esteban82, I have released DCW 2.0.2. Two questions though:

  1. Not sure where MD5 numbers actually go for this?
  2. Where did we place the update-data server script? I have already forgotten...

@maxrjones
Copy link
Member Author

  1. I think this will be the first time we post the MD5 numbers. They could go in the release notes under the description.
  2. It needs to get merged from Add option to update files on the GMT dataserver #29. There's currently a conflict with the config file that will need to be resolved before merging.

@PaulWessel
Copy link
Member

OK, updated MD5 and fixed conflict in #29. I think I got this to the point that it worked for me but not for you, so I should be able to execute it, yes?

@maxrjones
Copy link
Member Author

Great, thanks. Yes, it should work.

@PaulWessel
Copy link
Member

I think all tasks have been completed. Thanks @Esteban82 and @meghanrjones. Let me know if we forgot something (and can then add to the checklist). I think with this release it is safe to work on the 2.1.0 version which will require the next GMT release to take advantage of the features.

@maxrjones
Copy link
Member Author

Great, thanks Paul and Federico!

@seisman
Copy link
Member

seisman commented Dec 16, 2021

Can you also provide the sha256sum? It's used in many other distributors like conda-forge and homebrew.

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

No branches or pull requests

4 participants