Should we remove the 0.x.x releases?

[TimUntersberger]

I feel like this just causes confusion and problems.

@ramirezmike any thoughts?

[ramirezmike]

that's tough.. I see how it's confusing since the latest documentation doesn't apply to the latest release, but I'm also not sure what all you want to have implemented before a new release.

I don't think it'd be good to only have pre-release builds available... that would probably be confusing too. If we make a new release that'd solve the problem and we can increase how often we release for a little until it's pretty stable and then reevaluate?

[TimUntersberger]

but I'm also not sure what all you want to have implemented before a new release.

I honestly can't remember what my requirements where 🤷‍♂️.

If we make a new release that'd solve the problem and we can increase how often we release for a little until it's pretty stable and then reevaluate

👍

So should we just release the build of the current master or after you merge your PR?

[ramirezmike]

So should we just release the build of the current master or after you merge your PR?

personally, I'd like to get those deadlocks minimized before a release but I also don't know how much it affects others due to workflow or computer specs. have you encountered those at all?

I might not have time today to look at switching to SendNotifyMessage.. I'm ok with any of these options:

A) if you check out the deadlock branch and it works well for you, we can merge it into master and make a release and I can take a look at SendNotifyMessage in a future pull request

B) make a new release on existing master and some point soon merge the deadlocks branch into master (after checking out SendNotifyMessage) and make another small incremental release like a patch or whatever.

C) wait until I check out SendNotifyMessage and we think it's good and then merge into master and make a release