Is there a set release cycle/process for the Python package?

[FrankPortman]

I see the last release was Aug 8 and I'd really love some features off main, namely some bugfixes around schema overwrites. Not sure if there is a set cycle these release on. We tend to not pin to Github shas for packages at $DAY_JOB unless there is a really pressing reason (i.e. no new release on the horizon).

[rtyler]

There is not a fixed release cycle. A lot of it comes down to maintainer time and motivation 😄

As you might expect, we're always happy to have more help in reviewing changes, testing them out with real workloads, and validating that main is ready for release.

[FrankPortman]

In practice, how would I do that?

Are you guys open to people creating issues that are along the lines of "hey it's been a while since release and I feel like these are some pretty important and significant fixes since then which I can confirm work with my company's test suite, can you cut a new release?".

To be super transparent, that was basically my thought process around the time I made this discussion, but I approached it more as a question to double check rather than an explicit ask to cut a new release.

[rtyler]

I would say:

• Do: test off main and if a release is helpful for your organization, piping up in Slack is probably most helpful to say "hey y'all, this stuff is looking good, another release would be helpful"
• Do not: open an issue "when will the next Python release be made"

The latter is less than courteous in any open source project, but I am okay with a nudge that says "I have tested SHA@X against our internal test suite, I think it's ready for release" if a release hasn't been cut in a week or two