Redux-observable: About 2.0.0

[MaximeBernard]

I've been using redux-observable for quite some time now (and think everyone should) and love that ofType operator 👌 (cleaner TS & cleaner RX)

2.0.0-alpha.0 has been released for 1 year now and still no "stable" release.

1. Do you have any roadmap in mind?
2. Do you have any blocker?
3. So far, I've used 2.0.0-alpha.0 and didn't find any issue. Why not release it "as is" yet?
4. Do you need any help?

[NateAGeek]

Honestly since this has not really been met with a response worries me. Is there some actual committee of some sort?

[jayphelps]

@NateAGeek no committee. There have been a few people who have helped out here and there--been very grateful for them. Ultimately this project is in maintenance mode as I don't currently work on any UI projects myself right now. I didn't release 2.0 because at the time I didn't have cycles to support any potential problems that might arise after the release; which, in my experience, is common when you do make breaking changes as it does. Whereas the current "stable" release is battle hardened and the typical quirks you'd expect to find well known, relatively speaking. The docs would need to be updated to reflect the changes still. They're not massive, but I just don't have the cycles. I've asked a few people who use the project if they'd like to become maintainers, but none have. Which, really, isn't unexpected considering the time it can take if you're truly active with it. If someone wants to volunteer, lmk.

Knowing that, if someone has a legit counter argument for releasing 2.0.0 final, I'm open to hearing them. But (this goes to anyone, not just the people in this thread) not willing to listen to attacks. This is open source, and there is no warranty expressed or implied. Claiming contrary only pushes me further away from wanting to help. I caveat that because part of the reason I have stepped back from open source in general is the abuse and take-without-giving attitude of so many; though I've also been busy with my own startup and haven't worked on a redux project in some years.

[jayphelps]

@MaximeBernard

Here are my current thoughts to your questions:

Do you have any roadmap in mind?

I do not, unfortunately. I'm not currently working on any UI at all (I'm mostly working on compiler stuff related to my startup) and also haven't worked on an app that needed redux in several years.

Do you have any blocker?

Before, it was mostly around that several people wanted other changes in 2.0 that I hadn't gotten to yet and didn't have time for. Now it's mostly that I know if I release 2.0 as stable, it's what people will use by default, which means if there are new problems, I'd have to either support them or ignore them. The current stable version, on the other hand, is quite stable. And though it does have quirks (as all libraries do) they're quite minor IMO.

Also the docs need some changes, but they're relatively minor (I think?)

So far, I've used 2.0.0-alpha.0 and didn't find any issue. Why not release it "as is" yet?

Same answer as above.

Do you need any help?

Would love some if you still happen to have time! No pressure, of course. This is all volunteer work. If you're interested in helping, or even becoming a maintainer, you can reach out through email (in profile) or Twitter DMs.

[NateAGeek]

@jayphelps I'm sorry to hear the struggle with "take-without-giving attitude", and I know this is one of the issues with open source projects. I did not want my comment to push that narrative, however, I just was not sure about the state of the project. I appreciate the time and thank you for responding to my question.

I hope to offer support if my personal project kicks off. Best of luck with your startup and thank you again for the time and clarification.

[jayphelps]

@NateAGeek Thanks!

@everyone I added a note in the README in this PR if anyone has feedback: #744

[evertbouw]

I'm also no longer working with redux-observable after switching jobs. Feel free to tag me in issues/PRs tho