Was not what I said. Said doc will be part of 7.0.0 delivery and therefore vote. Le 27 avr. 2016 22:43, "David Blevins" <[email protected]> a écrit :
> I did vote. -1 for 7.0.0 final being the first release with Tomcat 8.5. > And definite -1 to start voting before we have docs ready that describe > what state TomEE 7 is in. > > What I really would not want to see happen is that the documentation > effort of TomEE 7’s status be seen as a separate effort and “they” better > hurry up or “we” will eventually get impatient and click the publish button > without them. > > I’d love to see us approach that effort together and everyone chip in. I > don’t think 72 hours is enough time to flush out all the materials we’d > like to create for a major release that will have some communication > challenges. > > > -David > > > > On Apr 26, 2016, at 2:42 PM, Romain Manni-Bucau <[email protected]> > wrote: > > > > @David: you didnt really vote. M4 is not an option of this thread, > putting > > the doc in vote with 7.0 is a good idea we should do IMO. If you want to > > participate to the vote please do or your opinion will not be part of the > > result. > > > > Side note: if 7.0.0 is ok I'll try to gather what we need in a quick > thread > > before starting vote process. > > Le 26 avr. 2016 23:31, "David Blevins" <[email protected]> a > écrit : > > > >> My vote would be for an immediate M4 to flush out any issues with 7.0 > >> while we work on the proper way to communicate the eventual 7.0 GA > status > >> and how-tos. > >> > >> I would be -1 for moving forward with 7.0 votes and letting “someone > else” > >> get the documentation in order out of fear there would be a “meh, you > >> didn’t keep up with me, ok out the door with 7.0 and no documentation.” > >> > >> I don’t think we could survive a miscommunication on this sensitive > topic > >> and would want to see it as top priority ahead of any 7.0 GA release. > >> > >> > >> -- > >> David Blevins > >> http://twitter.com/dblevins > >> http://www.tomitribe.com > >> > >>> On Apr 25, 2016, at 5:01 AM, Romain Manni-Bucau <[email protected] > > > >> wrote: > >>> > >>> Hi guys, > >>> > >>> seems we'll reach a consensus soon on the fact we have to use 7.0 for > >> next > >>> release so trying to make the global topic moving forward ie the next > >> tomee > >>> release version. > >>> > >>> Using milestones doesn't reflect code state and has the following > >>> disadvantages: > >>> > >>> - we have no clue yet we'll sort soon oracle discussions > >>> - it prevents tooling and cloud integration (this thread is not about > >>> discussing it is for good reasons or bad) > >>> - milestones seems to impact some user/manager minds where it can be > more > >>> stable than some previous final releases, then also impacts us as a > >>> community since we don't reach the usage we should > >>> - we are stable since months, if we stop we can still change the > version > >>> later if desired but today we are > >>> > >>> To make it clear this is a VOTE by LAZY consensus to use 7.0.0 as next > >>> tomee release version. > >>> > >>> [+1] yes let's do it > >>> [ 0] what are you speaking about? meh don't care > >>> [-1] no cause ${reason} is a blocker > >>> > >>> Vote is open for 72 hours. > >>> > >>> Romain Manni-Bucau > >>> @rmannibucau <https://twitter.com/rmannibucau> | Github > >>> <https://github.com/rmannibucau> | LinkedIn > >>> <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory > >>> <https://javaeefactory-rmannibucau.rhcloud.com> > >> > >> > >
