A part from the immediate next release, I would also start the discussion for a more longer term changes.
Several weeks ago we discussed about changes that required some degree of compatibility breaking, not in the APIs but rather in the tools/configuration or in form of binary compatibility. For these changes, we might want to do a 2.0 release, and while we're at it we should take the opportunity to make all the changes we need. I would like to start getting the discussion on all the proposals for these changes and I've setup a github project for tracking purposes: https://github.com/apache/incubator-pulsar/projects/4 I would expect that getting all the changes for 2.0 might take more than the regular ~1month release cycle. We could plan to have a 1.21/1.22 in the middle if that becomes necessary. What are the thoughts around this? Please, start adding tasks in the 2.0 project board and start the discussion here in the mailing list, even though a complete design/PIP is not ready. Matteo -- Matteo Merli <mme...@apache.org>
