The discussion is open😊. Basically if you a task is important for you, grab it. I will support you as needed to get to the right places in the project or to do/review the work needed...
If you think more discussion is useful, open a new email thread... J Anatole Am Mi., 2. Jan. 2019, 16:16 hat Aaron Coburn <acob...@apache.org> geschrieben: > Hi All, > > I agree that the next steps here should result in a release. I am eager to > make use of the new features and bug fixes that are currently in the > various master branches. I also have some time in the next few weeks to > help move this forward. > > Are there particular tasks or JIRA issues that should be resolved before > the next release? > > Best, Aaron > > > On Dec 15, 2018, at 8:20 AM, Anatole Tresch <atsti...@gmail.com> wrote: > > > > 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* > >
