Release schedule

[christianbundy]

Hey there! Is there a release schedule for this project? I'll often bump into bugs and then see the fix merged, but we'll often go a while without a new release. Is there a regular cadence that we're aiming to make releases on, or anything that I can do to help reduce the maintenance burden of cutting a new release?

[sobolevn]

No 🙂

I am the only one doing releases in my free time.

I think that there's only one way we can automate this: https://github.com/semantic-release/semantic-release

But, I am not sure that this is a good idea.

[christianbundy]

Is this something that I can help with? Totally understand if you aren't comfortable adding permissions, but I've maintained loads of open source projects (mostly in the Node.js ecosystem) and would love to help with the "create a tag and push a release" chore.

[sobolevn]

I am totally fine with automating this process 🙂
I think that we can push to PyPI from GitHub itself.

[SmileyChris]

For a bit more control, you can have the action to push to pypi trigger only when you create a github release rather than implicitly when a tag is created: https://www.caktusgroup.com/blog/2021/02/11/automating-pypi-releases/

[intgr]

I notice that Kurnikov has also made releases in the past. Since Sobolev is busy, any chance @mkurnikov you have time to make a release? This is holding up mypy 0.950 adoption (released on 27 April).

[mkurnikov]

Hi, I've made a 1.11.0 release from the latest master, please check that everything works as expected.

[mkurnikov]

I think new PyPI releases could be created on every release tag in the repo, it will simplify release maintenance a little bit. I do not have enough time and experience with GitHub actions to be able to do it though.
So, @christianbundy, if you'd like to create such a workflow, I can add the PyPI token to the Github Secrets later.

Also, feel free to tag me if you need a release. I do not have enough context to review code anymore, but I can manage that much.

[christianbundy]

Excellent. I know I'll be pretty busy with work this week, but I'll ping you when I've got something put together.

[mkurnikov]

I'll try to implement it myself this week, feel free to take it over if it's not yet done by the end of Sunday.

…

On Tue, May 24, 2022, 18:03 Christian Bundy ***@***.***> wrote: Excellent. I know I'll be pretty busy with work this week, but I'll ping you when I've got something put together. — Reply to this email directly, view it on GitHub <#959 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAR3XQ3M2EBSMVZKXSWBYRDVLT4ULANCNFSM5WB6CMOQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[mkurnikov]

Aaand I probably won't have time for that, sorry, please take over. Tag me later if you need anything from me.

[terencehonles]

@christianbundy / @mkurnikov I added a simple workflow in #980

[intgr]

The latest discussion about release schedule has been in #1095, I'm closing this duplicate.