Hi all! I have started to try and backport some of the bugfixes on the latest master to the 0.9 branch, to be part of the 0.9.1 bugfixing release.
While doing this, I came across so many places where critical bugs were fixed as parts of larger refactorings. It is very hard to backport these bug fixes without applying the refactorings as well. These bug fixes include deadlocks in co-tasks (streaming), deadlocks in the checkpointing, error handling and canceling of streaming programs. In general, the cleanup work in the streaming API has been very intensive. I was wondering whether we should not fork the 0.9.1 release from the current master. There have been few API breaking changes so far, which would be easier to undo than to backport all the fixes. We could do the following: - Fork off 0.9.1 off master and continue with all high-availability work in the master - Remove all code related to the new webfrontend from the 0.9.1 branch - Undo the few API breaking changes, such as Gelly and Scala API modifications, to keep major version compatibility. Concerning the question "why not release master as 0.10": We have had a set of announcements concerning streaming graduation and HA in 0.10, which we would break if we release the current state as 0.10. Greetings, Stephan
