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
[RELEASE] Major Spoon Release 6.0.0: done. #1699
Comments
So, here comes the changelog. It contains a lot of bug fixes, but also some new features. I prefixed in the changelog the different changes that may break compatibility with previous Spoon release. Please note that a break in compatibility is not necessarily a breaking compatibility between binaries, but it can also be a change in the behaviour. For example, I say here that the change
is breaking: previous behaviour was to return Spoon continues to grow thanks to all our contributor who did again an amazing job for this release, so thanks to them! New features
Bug Fixes
Refactoring
Performance
Tests
Documentation
Other
Authors
|
impressive changelog! made some minor changes. |
FYI we postpone this release for next week: this will give us some time to merge #1707 and ensure it does not bring regression. |
@pvojtechovsky @monperrus Finally I propose to do the release of Spoon now - without CtImport - and we'll put ctimport and ctmodule in next release which will also be a major release then. WDYT? |
I don't mind waiting one more week for Spoon 6. |
If we also wait for CtModule it might be a lot more than one week :) |
When adding CtModule, is Spoon fully Java 9 compatible? |
It's the idea. On current snapshot Spoon already compiles with JDK9 but it does not process module-info.java information. |
Do it as you prefer. I agree, that 6.0 will be more stable if CtImport will be not in it. It is quite new ... |
Thank you very much @surli and @pvojtechovsky for all the effort put in this impressive release. |
Hi all,
we plan to do a release of Spoon 6.0.0 next week probably the 15th or the 16th.
This will be a major release potentially breaking API for some clients.
I will post later a changelog with specification of what exactly could be break with the new API.
The text was updated successfully, but these errors were encountered: