-
Notifications
You must be signed in to change notification settings - Fork 220
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
Comments
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. |
I'll do the change log. I can do the release (AKA push the green button) as well unless someone else wants to! |
@weiji14 Do we have a Zenodo DOI yet? |
@weiji14 I am grateful to be listed as a collaborator. |
Yep, the DOI for v0.3.1 will be
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). |
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). |
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? |
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. |
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 "[email protected]" ([email protected] was too short) if we want to start up a YouTube channel for tutorials and the like. |
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.
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. |
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. |
It's really annoying 🤦 |
@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 |
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. |
Release has been done on GitHub! |
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, |
Great work!!! Thanks for all your efforts 🚀 . |
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!
@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. |
Made some minor changes on your latest version @weiji14. Good night's sleep 😉. |
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. |
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 😫) |
Of course, please help polish it. I am heading off to bed and see you guys tomorrow. |
@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. |
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. |
I think you're right! FYI, xarray and pandas also use "_dev", and numpy uses "_team" 😃
|
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!
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 - |
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. |
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).
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)? |
Cool, I noticed you added back most
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. |
🤦 Good to know. Would it be better for me to change them back now?
Sounds good. |
The announcement is great. Thanks for the revisions @meghanrjones. |
ResearchGate announcement is posted. |
We have finished the v0.3.1 release! Great work! 🎉 |
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?
Document how to skip CI in the contributing guides (Document how to skip CI in the contributing guides #908)Before release:
doc/_static/version_switch.js
for documentation switcherRelease:
After release:
[Major/Minor releases only] GMT website (News)The text was updated successfully, but these errors were encountered: