0.12 release is being delayed because we haven't finish some issues scheduled to 0.12. There are many demands on 0.12 release. The main reason is much different code base between master and 0.11.x. Some users and developers want to fix bugs in 0.11.x as well as in master branch.
I think it's time to release 0.12 release with the current branch and some critical remain issues.
My question is two: * What do you think about it? * If we agree with 0.12. release, what issues must be included in this release?
Add to this, it seems like TAJO-1724[^1] and TAJO-1951[^2] was originally aimed to be fixed in 0.12.0 but still not on progress. Could you change their (expected) fix version to later one? And if there is anyone who is working on those issues, I would like to take them.
If you guys were doing issues scheduled to 0.12, please change fix versions.
Dongjin, Sure. You can freely change the schedule.
Best regards, Hyunsik
On Tue, Sep 13, 2016 at 8:21 AM Dongjin Lee <[EMAIL PROTECTED]> wrote:
NEW: Monitor These Apps!
Apache Lucene, Apache Solr and all other Apache Software Foundation project and their respective logos are trademarks of the Apache Software Foundation.
Elasticsearch, Kibana, Logstash, and Beats are trademarks of Elasticsearch BV, registered in the U.S. and in other countries. This site and Sematext Group is in no way affiliated with Elasticsearch BV.
Service operated by Sematext