-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Comments
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. |
Even another RC release would be nice. This issue was fixed since 4.0.0-rc.2: Would love to have access to that. |
Another two months have passed, what's the status of this project? I would also love to have another release. |
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 ? |
I wonder if it's a time to a fork, |
@oriSomething I think David means the I'd rather have the maintainers reconsider #1005 before thinking about a hard-fork. |
@philipp-spiess Of course better to have more maintainers. But it seems for a long time that nothing really happens here. |
Yeah I was talking about master going from rc2 to final... |
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. |
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. |
Yes - Kind of feel like @thomhos about the fact that inactivity on a repo may lead me to re-think upgrading to 4-rc2... |
Hey all, thanks for your continued patience. I'm working on an upgrade
strategy for a final v4 release as well as looking for additional
maintainers.
This project is definitely not dead, as we're using it in many projects,
but it's certainly been in hibernation recently.
…On Fri, Aug 25, 2017 at 1:16 PM David ***@***.***> wrote:
Yes - Kind of feel like @thomhos <https://github.com/thomhos> about the
fact that inactivity on a repo may lead me to re-think upgrading to 4-rc2...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1215 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AADD0qOHGA1-FACIEwHFPsSvJ_QtDeSVks5sbyuxgaJpZM4NG-Mp>
.
|
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! |
@leebyron Is this search for maintainers purely internal to Facebook, or are you also open to maintainers from the broader community? |
@asazernik +1. @leebyron I would love to help as a maintainer. |
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 |
Hi, it's been several months since this was closed, and still no release. I'd like to re-open this issue. |
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!
The text was updated successfully, but these errors were encountered: