Stream: python

Topic: ✔ old milestones

view this post on Zulip Philip Durbin 🚀 (Feb 14 2024 at 20:02):

Here's the text I'm using when removing issues from old milestones:

As discussed during the 2024-02-14 meeting of the pyDataverse working group, we are closing old milestones in favor of a new project board at https://github.com/orgs/gdcc/projects/1 and removing issues (like this one) from those old milestones. Please feel free to join the working group! You can find us at https://py.gdcc.io and https://dataverse.zulipchat.com/#narrow/stream/377090-python

Markdown version, for easy copy/paste if we want to reuse it:

As discussed during the [2024-02-14 meeting](https://docs.google.com/document/d/1FH77wrCgh7FqB6uTsap_Thll0JBf5O3_cjK9wcGU-3g/edit?usp=sharing) of the [pyDataverse working group](https://py.gdcc.io), we are closing old milestones in favor of a new project board at https://github.com/orgs/gdcc/projects/1 and removing issues (like this one) from those old milestones. Please feel free to join the working group! You can find us at https://py.gdcc.io and https://dataverse.zulipchat.com/#narrow/stream/377090-python

view this post on Zulip Philip Durbin 🚀 (Feb 14 2024 at 20:03):

I mentioned that only a few issues were opened by people other than Stefan. Here's one: https://github.com/gdcc/pyDataverse/issues/86

view this post on Zulip Philip Durbin 🚀 (Feb 14 2024 at 20:13):

Another one: https://github.com/gdcc/pyDataverse/issues/9

view this post on Zulip Philip Durbin 🚀 (Feb 14 2024 at 20:14):

Another: https://github.com/gdcc/pyDataverse/issues/42

view this post on Zulip Philip Durbin 🚀 (Feb 14 2024 at 20:14):

and https://github.com/gdcc/pyDataverse/issues/112

view this post on Zulip Philip Durbin 🚀 (Feb 14 2024 at 20:17):

ooo, this one's a PR: https://github.com/gdcc/pyDataverse/pull/62

view this post on Zulip Philip Durbin 🚀 (Feb 14 2024 at 20:17):

another: https://github.com/gdcc/pyDataverse/issues/118

view this post on Zulip Philip Durbin 🚀 (Feb 14 2024 at 20:20):

last one for 0.4.0: https://github.com/gdcc/pyDataverse/issues/136

view this post on Zulip Philip Durbin 🚀 (Feb 14 2024 at 20:21):

Ok, I closed 0.4.0: https://github.com/gdcc/pyDataverse/milestone/4

view this post on Zulip Philip Durbin 🚀 (Feb 14 2024 at 20:22):

0.4.0 was the one I said I'd handle. It was a big one!

view this post on Zulip Philip Durbin 🚀 (Feb 14 2024 at 20:22):

Across the remaining milestones there are only 24 issues. 14 in 0.5.0 and 10 in "Later".

view this post on Zulip Philip Durbin 🚀 (Feb 14 2024 at 20:22):

I'm happy to handle these too. Just lemme know.

view this post on Zulip Philip Durbin 🚀 (Feb 14 2024 at 20:28):

I just closed 0.3.0 because it didn't have any open issues. Besides the current version of pyDataverse is newer: 0.3.1.

view this post on Zulip Jan Range (Feb 15 2024 at 10:05):

Thanks @Philip Durbin for going through the milestones :dataverse_man: I will review the PRs and issues from others to see if we want to use this for the next version.

If it is alright for you to continue, that would be great. Otherwise, I can also go through the 0.5.0 issues :-)

view this post on Zulip Philip Durbin 🚀 (Mar 04 2024 at 16:50):

Sure, no problem. I just added the note the remaining issues that had milestones. Then I removed the milestone and closed the milestone. All done! No open milestones! https://github.com/gdcc/pyDataverse/milestones

And no more confusion, hopefully. :grinning:

view this post on Zulip Notification Bot (Mar 04 2024 at 16:51):

Philip Durbin has marked this topic as resolved.

Last updated: Nov 01 2025 at 14:11 UTC