First of all I would like to welcome our new committers, William and Aaron. It is really great to have you on board! Given that I would propose, we should shortly discuss the next steps to be done, whcih I strongly beleive is a release. The things I see for doing so are:
- we check any JIRA open tickets and Github pull requests (most of the open pull requests should be already included, but I would like to check that before closing them) - we should decide on any other issue in JIRA, if it should be fixed with the next release. - we should decide given the API/SPI changes reported by revapi on the release number. - we should check for quality issues in Javadocs and code and improve the method coverage to 80%, covering hereby all non trivial code parts. I already did this for the API project (not yet pushed everything) and started doing so for the spisupport and core packages. - Documentation and web is already ready, so we can focus on the code parts mainly. - From a feature aspect I propose the state as of now should be the scope for the next release. This includes additionally collection support, and property sources for using consul, hazelcast and etcd as a backend. Does anybody have more input or ideas, so please give a shout. I would try to taskify these things and create JIRA tickets for all of them, so we can grab things we want to do and prevent doing things twice. Looking forward to any comments! J Anatole -- *Anatole Tresch* PPMC Member Apache Tamaya JCP Star Spec Lead *Switzerland, Europe Zurich, GMT+1* *maketechsimple.wordpress.com <http://maketechsimple.wordpress.com/> * *Twitter: @atsticks, @tamayaconf*
