Tag request

[vfazio]

I'd like to request a new tag/release.

Ideally we'd get at least #240 in. I would also like at least the fixes for the resource leaks in #238. We may have to defer the fix for the hang after baking it for a while.

The biggest driver for us is dropping websockets since the pinned version does not have 3.13 wheels available. This is currently blocking our migration to a newer version of Python (and of websockets).

If it's preferable to cut multiple tags to have the ability to release some changes and yank as necessary, then maybe we release what's in-tree currently with a subset of the changelog from #240 and then do a subsequent release for the dropping of 3.9 and other fixes.

Open to ideas, I don't want to be a nuisance!

[vfazio]

The reason i threw out the idea of multiple tags is because none of the changes in-tree since 0.3.0 and in #240 actually change behavior. The change to the stream management to resolve the resource leaks and to resolve the hang do affect functionality, so a 0.4.0 cut should be functionally equivalent to 0.3.0 with the need for users to migrate their use of rpcx.websockets to their own implementation based on the example code.

[uSpike]

Id rather not maintain a separate branch for an old release.

[uSpike]

Happy to cut a new release once things are merged tho

[vfazio]

Oh, sure, I didn't mean to imply that a legacy branch needed to be maintained.

I guess I'm mostly thinking about the checkpoints at which we should consider bumping the version and cutting a tag.

I just merged #240. I could bump the version now in prep for the next release.

It does seem "dumb" to cut a tag shortly after another release, but I'm just trying to cover our bases so that in the event that there is some issue that arises due to the work in #238 that we can pin our dependency on a previous version and still maintain support for newer websockets and python 3.13.

That's why i was wondering if it made sense to:

• v0.4.0 with current main
• v0.4.x/v0.5.0 with changes from Client: Fix client hang after stream end #238 once it lands in main

so we could revert to 0.4.0 if something came up

[uSpike]

ah ok that sounds fine to me, we can do 2 releases