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 PyGMT v0.3.1 #987

Closed
22 of 23 tasks
willschlitzer opened this issue Mar 2, 2021 · 41 comments
Closed
22 of 23 tasks

Release PyGMT v0.3.1 #987

willschlitzer opened this issue Mar 2, 2021 · 41 comments
Labels
maintenance Boring but important stuff for the core devs
Milestone

Comments

@willschlitzer
Copy link
Contributor

willschlitzer commented Mar 2, 2021

Release: v0.3.1
Scheduled Date: 2021/03/14
Pull request due date: 2021/03/12

Priority PRs/issues to complete prior to release
@GenericMappingTools/python Any priorities to finish for this patch release?

Before release:

Release:

  • At the PyGMT release page on GitHub:
    • Edit the draft release notes with the finalized changelog
    • Set the tag version and release title to v0.3.1
    • Make a release by clicking the 'Publish Release' button, this will automatically create a tag too
  • Manually upload the pygmt-v0.3.1.zip file to https://zenodo.org/deposit, ensure that it is filed under the correct reserved DOI

After release:


  • Party 🎉 (don't tick before all other checkboxes are ticked!)
@willschlitzer willschlitzer added the maintenance Boring but important stuff for the core devs label Mar 2, 2021
@willschlitzer willschlitzer added this to the 0.3.1 milestone Mar 2, 2021
@seisman seisman pinned this issue Mar 2, 2021
@weiji14
Copy link
Member

weiji14 commented Mar 9, 2021

Alright, since we're getting close to the release date, I've moved a couple of lower priority issues from the v0.3.1 to v0.4.0 milestone. We should definitely prioritize wrapping up the gallery reorganization #876 in the next day or two (since a few other PRs depend on it). I'd encourage everyone to help out in reviewing the open PRs, and I see that quite a few people have stepped up which is good!

Afterwards, on 14 March (UTC), we'll need volunteers to help out with the following:

Just raise your hand 👋 up on what you'd like to help out with and you'll get the job. No interview required.

@willschlitzer
Copy link
Contributor Author

willschlitzer commented Mar 9, 2021

I'll do the change log. I can do the release (AKA push the green button) as well unless someone else wants to!

@willschlitzer
Copy link
Contributor Author

@weiji14 Do we have a Zenodo DOI yet?

@core-man
Copy link
Member

  • Any contributor wanting to be listed as a collaborator on PyGMT's ResearchGate profile, just ping me (or any other @GenericMappingTools/python member) and we'll get you added in.

@weiji14 I am grateful to be listed as a collaborator.

@weiji14
Copy link
Member

weiji14 commented Mar 10, 2021

@weiji14 Do we have a Zenodo DOI yet?

Yep, the DOI for v0.3.1 will be 10.5281/zenodo.4592991.

@weiji14 I am grateful to be listed as a collaborator.

Cool, just followed you on ResearchGate, you'll need to follow me back for me to add you as a collaborator according to https://www.researchgate.net/post/how_can_I_add_collaborators_to_an_existing_project (Same for anyone else wanting to join).

@michaelgrund
Copy link
Member

Alright, since we're getting close to the release date, I've moved a couple of lower priority issues from the v0.3.1 to v0.4.0 milestone. We should definitely prioritize wrapping up the gallery reorganization #876 in the next day or two (since a few other PRs depend on it). I'd encourage everyone to help out in reviewing the open PRs, and I see that quite a few people have stepped up which is good!

Afterwards, on 14 March (UTC), we'll need volunteers to help out with the following:

* [ ]  Start a PR for a new Changelog entry (see previous one at #887 and instructions at https://github.com/GenericMappingTools/pygmt/blob/master/MAINTENANCE.md#making-a-release

* [ ]  Draft a release announcement for the forum at https://hackmd.io/@pygmt (see previous one at https://hackmd.io/@pygmt/v0-3-0_announcement)

* [ ]  Social media outreach:
  
  * [ ]  Setup Twitter/Instagram as mentioned in the last release at [#845 (comment)](https://github.com/GenericMappingTools/pygmt/issues/845#issuecomment-779489746)
  * [ ]  If anyone has experience with writing a blog post, that would be a great contribution too!
  * [ ]  Any contributor wanting to be listed as a collaborator on [PyGMT's ResearchGate profile](https://www.researchgate.net/project/PyGMT-A-Python-interface-for-the-Generic-Mapping-Tools), just ping me (or any other @GenericMappingTools/python member) and we'll get you added in.

Just raise your hand 👋 up on what you'd like to help out with and you'll get the job. No interview required.

I will only be partially available on 14 March, however, if possible I could help out with updating the website etc. (as for the last release).

@maxrjones
Copy link
Member

Alright, since we're getting close to the release date, I've moved a couple of lower priority issues from the v0.3.1 to v0.4.0 milestone. We should definitely prioritize wrapping up the gallery reorganization #876 in the next day or two (since a few other PRs depend on it). I'd encourage everyone to help out in reviewing the open PRs, and I see that quite a few people have stepped up which is good!

Afterwards, on 14 March (UTC), we'll need volunteers to help out with the following:

* [ ]  Start a PR for a new Changelog entry (see previous one at #887 and instructions at https://github.com/GenericMappingTools/pygmt/blob/master/MAINTENANCE.md#making-a-release

* [ ]  Draft a release announcement for the forum at https://hackmd.io/@pygmt (see previous one at https://hackmd.io/@pygmt/v0-3-0_announcement)

* [ ]  Social media outreach:
  
  * [ ]  Setup Twitter/Instagram as mentioned in the last release at [#845 (comment)](https://github.com/GenericMappingTools/pygmt/issues/845#issuecomment-779489746)
  * [ ]  If anyone has experience with writing a blog post, that would be a great contribution too!
  * [ ]  Any contributor wanting to be listed as a collaborator on [PyGMT's ResearchGate profile](https://www.researchgate.net/project/PyGMT-A-Python-interface-for-the-Generic-Mapping-Tools), just ping me (or any other @GenericMappingTools/python member) and we'll get you added in.

Just raise your hand 👋 up on what you'd like to help out with and you'll get the job. No interview required.

Since I previously said I would, I can create a twitter account and then hopefully transfer it later on to someone who understands how to use emojis. Instagram is over my head though, sorry. Do you think GMT/PyGMT twitter should be the same or different?

@core-man
Copy link
Member

I am available, but I am not good at social media outreach. Maybe I can help draft a release announcement for the forum at https://hackmd.io/@pygmt if it does not need any permission.

@willschlitzer
Copy link
Contributor Author

Alright, since we're getting close to the release date, I've moved a couple of lower priority issues from the v0.3.1 to v0.4.0 milestone. We should definitely prioritize wrapping up the gallery reorganization #876 in the next day or two (since a few other PRs depend on it). I'd encourage everyone to help out in reviewing the open PRs, and I see that quite a few people have stepped up which is good!
Afterwards, on 14 March (UTC), we'll need volunteers to help out with the following:

* [ ]  Start a PR for a new Changelog entry (see previous one at #887 and instructions at https://github.com/GenericMappingTools/pygmt/blob/master/MAINTENANCE.md#making-a-release

* [ ]  Draft a release announcement for the forum at https://hackmd.io/@pygmt (see previous one at https://hackmd.io/@pygmt/v0-3-0_announcement)

* [ ]  Social media outreach:
  
  * [ ]  Setup Twitter/Instagram as mentioned in the last release at [#845 (comment)](https://github.com/GenericMappingTools/pygmt/issues/845#issuecomment-779489746)
  * [ ]  If anyone has experience with writing a blog post, that would be a great contribution too!
  * [ ]  Any contributor wanting to be listed as a collaborator on [PyGMT's ResearchGate profile](https://www.researchgate.net/project/PyGMT-A-Python-interface-for-the-Generic-Mapping-Tools), just ping me (or any other @GenericMappingTools/python member) and we'll get you added in.

Just raise your hand 👋 up on what you'd like to help out with and you'll get the job. No interview required.

Since I previously said I would, I can create a twitter account and then hopefully transfer it later on to someone who understands how to use emojis. Instagram is over my head though, sorry. Do you think GMT/PyGMT twitter should be the same or different?

Unfortunately "@pygmt" on Twitter is a suspended account; I think keeping PyGMT the same as the GMT Twitter is fine for now; I don't foresee the project tweeting that often.

Also, I registered "pygmt.dev@gmail.com" (pygmt@gmail.com was too short) if we want to start up a YouTube channel for tutorials and the like.

@weiji14
Copy link
Member

weiji14 commented Mar 12, 2021

I am available, but I am not good at social media outreach. Maybe I can help draft a release announcement for the forum at https://hackmd.io/@pygmt if it does not need any permission.

Cool, just sent a hackmd invite to you and @michaelgrund too. I think most everybody is in but let me know if anyone else wants to join.

Since I previously said I would, I can create a twitter account and then hopefully transfer it later on to someone who understands how to use emojis. Instagram is over my head though, sorry. Do you think GMT/PyGMT twitter should be the same or different?

Unfortunately "@pygmt" on Twitter is a suspended account; I think keeping PyGMT the same as the GMT Twitter is fine for now; I don't foresee the project tweeting that often.

Also, I registered "pygmt.dev@gmail.com" (pygmt@gmail.com was too short) if we want to start up a YouTube channel for tutorials and the like.

Thanks @willschlitzer for setting that up! I agree that using the same twitter handle for GMT/PyGMT is fine, people can always hashtag #pygmt to be more specific. Probably easier to use the GMT YouTube channel to post PyGMT content, but I'm sure we'll find a use for that email at some point.

@maxrjones
Copy link
Member

We're live on twitter! https://twitter.com/gmt_software

The 'handle' has to be 4+ characters (not GMT), less than 15 characters (not GenericMappingTools), and only alphanumeric characters and underscores. I came up with @gmt_software but if anyone has better ideas please feel free to share.

@seisman
Copy link
Member

seisman commented Mar 12, 2021

The 'handle' has to be 4+ characters (not GMT), less than 15 characters (not GenericMappingTools),

It's really annoying 🤦

@seisman
Copy link
Member

seisman commented Mar 12, 2021

We're live on twitter! twitter.com/gmt_software

The 'handle' has to be 4+ characters (not GMT), less than 15 characters (not GenericMappingTools), and only alphanumeric characters and underscores. I came up with @gmt_software but if anyone has better ideas please feel free to share.

@meghanrjones Did you ask Leo or Paul if there is already a GMT (maybe suspended) Twitter account? I have the impression Leo may already create one.

@maxrjones
Copy link
Member

We're live on twitter! twitter.com/gmt_software
The 'handle' has to be 4+ characters (not GMT), less than 15 characters (not GenericMappingTools), and only alphanumeric characters and underscores. I came up with @gmt_software but if anyone has better ideas please feel free to share.

@meghanrjones Did you ask Leo or Paul if there is already a GMT (maybe suspended) Twitter account? I have the impression Leo may already create one.

I did not think this was the case but am double-checking now.

@weiji14
Copy link
Member

weiji14 commented Mar 14, 2021

We're live on twitter! twitter.com/gmt_software
The 'handle' has to be 4+ characters (not GMT), less than 15 characters (not GenericMappingTools), and only alphanumeric characters and underscores. I came up with @gmt_software but if anyone has better ideas please feel free to share.

@meghanrjones Did you ask Leo or Paul if there is already a GMT (maybe suspended) Twitter account? I have the impression Leo may already create one.

I did not think this was the case but am double-checking now.

What about @gmt_maps? or @gmt_team? Feel like @gmt_software is a bit of a handful to type.

@michaelgrund
Copy link
Member

Made some minor changes to the hackmd draft and added a question about the correct form (is it GMT 6.2. or GMT 6.2.0?).

@core-man
Copy link
Member

Made some minor changes to the hackmd draft and added a question about the correct form (is it GMT 6.2. or GMT 6.2.0?).

Thanks. You are right. It is GMT 6.2.0. The highlights at https://hackmd.io/@pygmt/v0-3-1_announcement were directly copied from the changelog draft in #1047 and will be updated when that PR is merged.

@willschlitzer
Copy link
Contributor Author

Release has been done on GitHub!

@weiji14
Copy link
Member

weiji14 commented Mar 14, 2021

And we are live on PyPI https://pypi.org/project/pygmt/0.3.1! I'll double check the package before uploading to Zenodo, got too paranoid with Murphy's Law during the last release. Edit: Ok, pip install pygmt==0.3.1 looks good and I've uploaded the Zenodo release which is now live on https://doi.org/10.5281/zenodo.4592991!

@michaelgrund
Copy link
Member

Great work!!! Thanks for all your efforts 🚀 .

@weiji14
Copy link
Member

weiji14 commented Mar 14, 2021

Good work team, I'm heading off to bed so will delegate the rest to you all. No rush to do them, please enjoy the rest of your Sunday first!

After release:

  • Update conda-forge pygmt-feedstock [Usually done automatically by conda-forge's bot]

@willschlitzer, will leave this to you.

Someone new could give this a go, see GenericMappingTools/try-gmt#13 for an example.

Let's do the announcements on Monday (UTC time), I've edited the draft at https://hackmd.io/@pygmt/v0-3-1_announcement a bit (to put the new contributors up front) but definitely needs a bit more polish. @core-man, will leave it to you to post it up there when everyone's given it a thumbs up.

@michaelgrund
Copy link
Member

Let's do the announcements on Monday (UTC time), I've edited the draft at https://hackmd.io/@pygmt/v0-3-1_announcement a bit (to put the new contributors up front) but definitely needs a bit more polish. @core-man, will leave it to you to post it up there when everyone's given it a thumbs up.

Made some minor changes on your latest version @weiji14. Good night's sleep 😉.

@core-man
Copy link
Member

core-man commented Mar 14, 2021

Great global team work. It seems the PyGMT team is working 24 hours a day. Thanks to everyone. I've learned a lot during the last several weeks.

BTW, I'm going to use some gallery and tutorial examples to give a preliminary introduction to PyGMT to the Seismological Group at our university (i.e., Nanyang Technological University, Singapore) next week. See a draft tutorial repository. Hope to help more and more GMT (bash) users know and use PyGMT 😄, just like you guys did.

@maxrjones
Copy link
Member

maxrjones commented Mar 14, 2021

Let's do the announcements on Monday (UTC time), I've edited the draft at https://hackmd.io/@pygmt/v0-3-1_announcement a bit (to put the new contributors up front) but definitely needs a bit more polish. @core-man, will leave it to you to post it up there when everyone's given it a thumbs up.

Made some minor changes on your latest version @weiji14. Good night's sleep 😉.

I have a couple recommended changes to the draft. Is it too late for me to edit the announcement? (obligatory grumble about the U.S. time shift today making this even hard to track 😫)

@core-man
Copy link
Member

core-man commented Mar 14, 2021

Let's do the announcements on Monday (UTC time), I've edited the draft at https://hackmd.io/@pygmt/v0-3-1_announcement a bit (to put the new contributors up front) but definitely needs a bit more polish. @core-man, will leave it to you to post it up there when everyone's given it a thumbs up.

Made some minor changes on your latest version @weiji14. Good night's sleep 😉.

I have a couple recommended changes to the draft. Is it too late for me to edit the announcement? (obligatory grumble about the U.S. time shift making this even hard to track 😫)

Of course, please help polish it. I am heading off to bed and see you guys tomorrow.

@maxrjones
Copy link
Member

We're live on twitter! twitter.com/gmt_software
The 'handle' has to be 4+ characters (not GMT), less than 15 characters (not GenericMappingTools), and only alphanumeric characters and underscores. I came up with @gmt_software but if anyone has better ideas please feel free to share.

@meghanrjones Did you ask Leo or Paul if there is already a GMT (maybe suspended) Twitter account? I have the impression Leo may already create one.

I did not think this was the case but am double-checking now.

What about @gmt_maps? or @gmt_team? Feel like @gmt_software is a bit of a handful to type.

@gmt_team is nice! I can update it to that before making the twitter announcement unless there are any other recommendations.

Regarding other accounts, Paul wasn't aware of any and I haven't heard back from Leo (which is good, since it's a weekend). My memory of the 2020-11-19 community meeting was that the previous attempt to create an account failed and that a new one would be necessary. The community meeting notes just say 'Twitter: Leo and Meghan can do twitter' which doesn't provide a definitive answer.

@seisman
Copy link
Member

seisman commented Mar 14, 2021

There is already a Twitter user called "gmt_team", which was created in Jan 2017, almost the same time that Leo started his postdoc in Hawaii. That's why I'm wondering if this "gmt_team" account was created by him.

If "gmt_team" is not available, what about "gmt_dev"?

@maxrjones
Copy link
Member

There is already a Twitter user called "gmt_team", which was created in Jan 2017, almost the same time that Leo started his postdoc in Hawaii. That's why I'm wondering if this "gmt_team" account was created by him.

If "gmt_team" is not available, what about "gmt_dev"?

gmt_dev is fine too. I don't think that account is associated with Leo. The gmt_team user is only following one person who goes by GMT and is not related to the GenericMappingTools.

@seisman
Copy link
Member

seisman commented Mar 14, 2021

The gmt_team user is only following one person who goes by GMT and is not related to the GenericMappingTools.

I think you're right!

FYI, xarray and pandas also use "_dev", and numpy uses "_team" 😃

@maxrjones
Copy link
Member

FYI, xarray and pandas also use "_dev", and numpy uses "_team" 😃

* xarray: https://twitter.com/xarray_dev

* pandas: https://twitter.com/pandas_dev

* numpy: https://twitter.com/numpy_team

Nice! Let's go with gmt_dev, since it's available. It should be all set to go now.

@weiji14
Copy link
Member

weiji14 commented Mar 14, 2021

Nice! Let's go with gmt_dev, since it's available. It should be all set to go now.

Wow, there's already 66 followers (and counting) at https://twitter.com/gmt_dev after the forum announcement!

I have a couple recommended changes to the draft. Is it too late for me to edit the announcement? (obligatory grumble about the U.S. time shift making this even hard to track tired_face)

Of course, please help polish it. I am heading off to bed and see you guys tomorrow.

Did another round of editing the draft at https://hackmd.io/@pygmt/v0-3-1_announcement. I'd appreciate a bit more proof-reading, and would prefer it if someone else does the forum post it this time (literally just copying and pasting the markdown into a box!). We can then do the ResearchGate and Twitter announcement after.

@maxrjones
Copy link
Member

Nice! Let's go with gmt_dev, since it's available. It should be all set to go now.

Wow, there's already 66 followers (and counting) at https://twitter.com/gmt_dev after the forum announcement!

I have a couple recommended changes to the draft. Is it too late for me to edit the announcement? (obligatory grumble about the U.S. time shift making this even hard to track tired_face)

Of course, please help polish it. I am heading off to bed and see you guys tomorrow.

Did another round of editing the draft at https://hackmd.io/@pygmt/v0-3-1_announcement. I'd appreciate a bit more proof-reading, and would prefer it if someone else does the forum post it this time (literally just copying and pasting the markdown into a box!). We can then do the ResearchGate and Twitter announcement after.

I can do the forum post. I did not really understand this statement in the announcement - version v0.3.1, a release with more than a handful of new gallery examples. Is this stating that the number of new gallery examples is more than a handful or that the release includes more than just new gallery examples?

@maxrjones
Copy link
Member

One other question about the forum announcement - would it be better for the highlights to link to the new pages rather than the PRs? The PRs can be found in the changelog and I expect that forum readers might be more interested in the product rather than the process.

@weiji14
Copy link
Member

weiji14 commented Mar 15, 2021

I can do the forum post. I did not really understand this statement in the announcement - version v0.3.1, a release with more than a handful of new gallery examples. Is this stating that the number of new gallery examples is more than a handful or that the release includes more than just new gallery examples?

Cool, please do make the post! We do have a more than 5 new gallery examples, and that's what I meant by a handful, but probably nice if we can rephrase it a bit (feel free to make the change).

One other question about the forum announcement - would it be better for the highlights to link to the new pages rather than the PRs? The PRs can be found in the changelog and I expect that forum readers might be more interested in the product rather than the process.

Good idea. Those were just copied from the highlights section in the changelog, but you're right that we could just link to the output (though not sure what to do about the point on #995).

@maxrjones
Copy link
Member

I can do the forum post. I did not really understand this statement in the announcement - version v0.3.1, a release with more than a handful of new gallery examples. Is this stating that the number of new gallery examples is more than a handful or that the release includes more than just new gallery examples?

Cool, please do make the post! We do have a more than 5 new gallery examples, and that's what I meant by a handful, but probably nice if we can rephrase it a bit (feel free to make the change).

One other question about the forum announcement - would it be better for the highlights to link to the new pages rather than the PRs? The PRs can be found in the changelog and I expect that forum readers might be more interested in the product rather than the process.

Good idea. Those were just copied from the highlights section in the changelog, but you're right that we could just link to the output (though not sure what to do about the point on #995).

OK, I made some changes but feel free to change it back if you prefer. Do you have a preference for whether the forum and twitter announcements are made tonight or tomorrow morning (EST | UTC-4)?

@weiji14
Copy link
Member

weiji14 commented Mar 15, 2021

OK, I made some changes but feel free to change it back if you prefer.

Cool, I noticed you added back most @username links to GitHub. More just a minor point, but most of us have the same Github handle as on the GMT forum (myself @weiji14 included) and we could just use plain @someone instead of [@someone](https://github.com/someone).

Do you have a preference for whether the forum and twitter announcements are made tonight or tomorrow morning (EST | UTC-4)?

Let's do the forum announcement now (or as soon as possible). I can do the twitter announcement if you want (coordinate on the Slack channel), and I think @core-man should do the ResearchGate announcement.

@maxrjones
Copy link
Member

OK, I made some changes but feel free to change it back if you prefer.

Cool, I noticed you added back most @username links to GitHub. More just a minor point, but most of us have the same Github handle as on the GMT forum (myself @weiji14 included) and we could just use plain @someone instead of [@someone](https://github.com/someone).

🤦 Good to know. Would it be better for me to change them back now?

Do you have a preference for whether the forum and twitter announcements are made tonight or tomorrow morning (EST | UTC-4)?

Let's do the forum announcement now. I can do the twitter announcement if you want (coordinate on the Slack channel), and I think @core-man should do the ResearchGate announcement.

Sounds good.

@maxrjones
Copy link
Member

maxrjones commented Mar 15, 2021

Forum announcement is posted!
Twitter announcement is posted!

@core-man
Copy link
Member

The announcement is great. Thanks for the revisions @meghanrjones.

@core-man
Copy link
Member

core-man commented Mar 15, 2021

ResearchGate announcement is posted.

@seisman
Copy link
Member

seisman commented Mar 15, 2021

We have finished the v0.3.1 release! Great work! 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
maintenance Boring but important stuff for the core devs
Projects
None yet
Development

No branches or pull requests

6 participants