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
Question: the road to 0.4 #85
Comments
Updating Guava classes is doable bit tricky. Also, so little of them is used that I am not sure it's worth it unless we found a bug. The shade plug-in did a real shitty job of slimming down the Guava classes; most likely do to the severe interdependencies of the code. For this reason the classes were copied in by hand and stripped of all but the used methods, plus those that had no dependencies. I'd say we ignore this for now. |
Sorry for not having followed up. Very busy at work then vacation. Here is the current status:
Once these 2 PR are merged, I think it could be a good idea to release a 0.4 version as we have people reporting already fixed issues. Edit: it might be a good idea to take a look at #89 too. But I'm not sure it's worth postponing a release if it's a complicated issue. FWIW, we develop our new applications using 0.4-SNAPSHOT for a while without any issues and it would be great to have an official release. Thanks! |
I agree with all you've said here. I will commit #91 & #84 ASAP. I will look into #89, although I believe it is a bit of a complicated issue and may be better off being put in the next release. Once these are settled I'll move to 0.4 release. It is long overdue & 0.4-SNAPSHOT had been working very well for quite a while. I believe I'll have this done before Monday. |
Nice. Thanks! |
Hi Kevin! Any news about the release? We're waiting for an official release before putting a few apps into production. Thanks! |
0.4 has finally been released... You'll notice I didn't specify which Monday 😁 |
Thanks Kevin! |
Hi,
Could we discuss the plan to release 0.4? A couple of important bugs have been fixed and it would be nice to release something.
My 2 cents: I would like to have this fixed before the release:
-> I can merge them/update them and create a new PR with only these commits updated to work with current develop branch.
See if we can fix:
#65
#81
Thanks for your feedback.
The text was updated successfully, but these errors were encountered: