We’re pleased to announce a first milestone release of Spring Statemachine 1.1.0.M1.
We released 1.0.0.M1 April 2015 and 1.0.0.RELEASE October 2015. We’ve also done 2 maintenance releases for 1.0.x series and now it’s time to look in a future with a 1.1.x series. 1.0.x enters into a maintenance mode while main development will focus on 1.1.x. This doesn’t mean that we’ll stop with 1.0.x, maintenance fixes for it will be done until we’re successfully transitioned beyond 1.1.x release. It is important in Spring projects to not drop maintenance until users are ready to move on into next minor/major release. We expect 1.0.x and 1.1.x live side by side until we fire out 1.2.x or 2.x series in foreseeable future.
What we actually got into this first milestone:
- Support for protecting events, transitions and actions with Spring Security.
- StateContext is now a first class citizen and has a bigger role both internally and how users interacts with it.
- Annotation model(@WithStateMachine) has been enhanced to match features from listeners and context events.
- Persist feature for Redis using Kryo serialization.
- Additional bug fixes and minor enhancements which were backported into 1.0.x.
- Two new samples using security and Redis persistence.
Full changes, as usual, is available from the changelog.
We added preliminary support for Session scoped beans for a state machine which has been a base for getting support for Spring Session. Further work is still work in progress waiting for next release from Spring Session 1.1.x order to support custom session serialization.
We’re planning to do the second milestone before a release candidate order to get into Spring IO release later this year around May(ish). We may do a final release when we’re ready but IO schedule is a final possible target date.
Thank you for all who have contributed in any way either via Stack Overflow, GitHub Issues or other channels. The driving force for changes really has been a community and requests from it.