Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Status update on 4.0.0 final release? #1215

Closed
pbomb opened this issue Apr 25, 2017 · 18 comments
Closed

Status update on 4.0.0 final release? #1215

pbomb opened this issue Apr 25, 2017 · 18 comments

Comments

@pbomb
Copy link

pbomb commented Apr 25, 2017

Hi @leebyron,

Sorry if this isn't the right place to ask for a status update on the 4.0.0 release. I'm sure there are many others who are also eagerly anticipating the release. Just curious if you have any guess on when it might be released or a list of issues you still want to close before releasing.

If this is not the right place to ask this question, feel free to close this issue.

Thanks for your hard work on this very useful library!

@hmeerlo
Copy link

hmeerlo commented May 18, 2017

Ok, so nothing happened to this repo for 2 months now, has it been abandoned? I'm really looking forward to the 4.0.0 release for better flowtype support.

@bhouser
Copy link

bhouser commented Jun 2, 2017

Even another RC release would be nice. This issue was fixed since 4.0.0-rc.2:
#1158

Would love to have access to that.

@kdudzik
Copy link

kdudzik commented Aug 2, 2017

Another two months have passed, what's the status of this project? I would also love to have another release.

@davidlygagnon
Copy link

davidlygagnon commented Aug 16, 2017

I was also wondering when 4.0.0 major release will happen? Last commit on 4.0.0-rc2 was in March, feels like this is being abandoned ?

@oriSomething
Copy link

@davidlygagnon
screen shot 2017-08-16 at 21 13 10

@oriSomething
Copy link

I wonder if it's a time to a fork, io.js style. I'm not sure. Also from legal point of view because of the PATENTS file.

@philipp-spiess
Copy link
Contributor

philipp-spiess commented Aug 16, 2017

@oriSomething I think David means the 4.0 work that is happening in the master branch. The branch 4.0-abandoned is from 2015.

I'd rather have the maintainers reconsider #1005 before thinking about a hard-fork.

@oriSomething
Copy link

@philipp-spiess Of course better to have more maintainers. But it seems for a long time that nothing really happens here.
Even if this stagnation called "stability" it seems that many PRs that can make daily use of this library easier end less bugs prune such as #1276 are not event get any response.
And I understand that the maintainer have no time or will which is okay. But it seems this project doesn't really open to new maintainers that aren't from Facebook, which makes this project stuck which is a sad thing since pretty much everywhere Immutable.js recommended to anyone who works with React event with all the buzz of "you might not need Redux and Immutable as well"

@davidlygagnon
Copy link

Yeah I was talking about master going from rc2 to final...

@skeet70
Copy link

skeet70 commented Aug 22, 2017

I'd also prefer we get more maintainers. If that's impossible because additional maintainers must be Facebook affiliated, forking seems like the only real option to keep the library going. I haven't seen any communication coming out of FB / @leebyron with regards to continued maintenance on this repo.

@thomhos
Copy link

thomhos commented Aug 23, 2017

It would be nice to know if maintenance is postponed, or being looked at, etc. At least some information would be nice. I was looking forward to using the v4 in a new typescript based project. But with the inactivity and obscurity around v4 I've decided not to use immutable, even though I'd really like to.

If we have some message from maintainers we at least know what to expect.

@davidlygagnon
Copy link

Yes - Kind of feel like @thomhos about the fact that inactivity on a repo may lead me to re-think upgrading to 4-rc2...

@leebyron
Copy link
Collaborator

leebyron commented Aug 25, 2017 via email

@thomhos
Copy link

thomhos commented Aug 25, 2017

Hey Lee, that's good to hear! I think we're all looking forward to a general status update when you've got some more information. But just this message is a good sign of life :)

Looking forward to the update for the typings!

@asazernik
Copy link

asazernik commented Sep 7, 2017

@leebyron Is this search for maintainers purely internal to Facebook, or are you also open to maintainers from the broader community?

@jonathanmarvens
Copy link

@asazernik +1. @leebyron I would love to help as a maintainer.

@leebyron
Copy link
Collaborator

Closing this issue since the next release is coming imminently.

For help - submitting high quality PRs fixing reported bugs, providing code review on existing PRs, and helping to answer questions and close out issues is the kind of thing I'm looking for help for.

Please feel free to just take action and ping me when a repo-owner action is needed

@steventrouble
Copy link

Hi, it's been several months since this was closed, and still no release. I'd like to re-open this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests