You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomee.apache.org by Romain Manni-Bucau <rm...@gmail.com> on 2016/04/25 14:01:31 UTC
[VOTE][LAZY] Next tomee release using 7.0.0 version
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>
Re: [VOTE][LAZY] Next tomee release using 7.0.0 version
Posted by Mark Struberg <st...@yahoo.de.INVALID>.
+1 no need to wait imo.
LieGrue,
strub
> Am 25.04.2016 um 14:01 schrieb Romain Manni-Bucau <rm...@gmail.com>:
>
> 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>
Re: [VOTE][LAZY] Next tomee release using 7.0.0 version
Posted by Romain Manni-Bucau <rm...@gmail.com>.
And here is my +1
with one -1 (binding) and 5 +1 bindings the vote passed.
updated http://tomee.apache.org/tomee-version-policies.html page to reflect
that. Feel free to enhance the page if anything is ambiguous or unclear for
you.
Thanks for your votes.
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>
2016-04-27 22:48 GMT+02:00 Romain Manni-Bucau <rm...@gmail.com>:
> 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" <da...@gmail.com> 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 <rm...@gmail.com>
>> 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" <da...@gmail.com> 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 <
>> rmannibucau@gmail.com>
>> >> 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>
>> >>
>> >>
>>
>>
Re: [VOTE][LAZY] Next tomee release using 7.0.0 version
Posted by Romain Manni-Bucau <rm...@gmail.com>.
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" <da...@gmail.com> 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 <rm...@gmail.com>
> 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" <da...@gmail.com> 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 <rmannibucau@gmail.com
> >
> >> 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>
> >>
> >>
>
>
Re: [VOTE][LAZY] Next tomee release using 7.0.0 version
Posted by David Blevins <da...@gmail.com>.
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 <rm...@gmail.com> 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" <da...@gmail.com> 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 <rm...@gmail.com>
>> 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>
>>
>>
Re: [VOTE][LAZY] Next tomee release using 7.0.0 version
Posted by Romain Manni-Bucau <rm...@gmail.com>.
@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" <da...@gmail.com> 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 <rm...@gmail.com>
> 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>
>
>
Re: [VOTE][LAZY] Next tomee release using 7.0.0 version
Posted by David Blevins <da...@gmail.com>.
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 <rm...@gmail.com> 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>
Re: [VOTE][LAZY] Next tomee release using 7.0.0 version
Posted by Andy Gumbrecht <ag...@tomitribe.com>.
+1 for 7.0.0 (documented status)
On 25 April 2016 at 14:56, Jonathan Gallimore <jg...@tomitribe.com>
wrote:
> On Mon, Apr 25, 2016 at 1:39 PM, Romain Manni-Bucau <rmannibucau@gmail.com
> >
> wrote:
>
> >
> > Does it clarify the intent?
> >
> >
> It does, thank you. Providing that TCK status is clearly documented with
> the release, and there are no legal issues, I have no objection to a 7.0.0.
>
> +1.
>
> Jon
> --
> Jonathan Gallimore
> http://twitter.com/jongallimore
> http://www.tomitribe.com
>
--
Andy Gumbrecht
https://twitter.com/AndyGeeDe
http://www.tomitribe.com
Re: [VOTE][LAZY] Next tomee release using 7.0.0 version
Posted by Jonathan Gallimore <jg...@tomitribe.com>.
On Mon, Apr 25, 2016 at 1:39 PM, Romain Manni-Bucau <rm...@gmail.com>
wrote:
>
> Does it clarify the intent?
>
>
It does, thank you. Providing that TCK status is clearly documented with
the release, and there are no legal issues, I have no objection to a 7.0.0.
+1.
Jon
--
Jonathan Gallimore
http://twitter.com/jongallimore
http://www.tomitribe.com
Re: [VOTE][LAZY] Next tomee release using 7.0.0 version
Posted by Jean-Louis Monteiro <jl...@tomitribe.com>.
+1 for 7.0.0 with Tomcat 8.5
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com
On Mon, Apr 25, 2016 at 2:46 PM, Jean-Louis Monteiro <
jlmonteiro@tomitribe.com> wrote:
> Same fear for me. We'll not get any Java EE 7 TCK at Apache. So waiting
> only penalize the project.
>
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
> On Mon, Apr 25, 2016 at 2:39 PM, Romain Manni-Bucau <rmannibucau@gmail.com
> > wrote:
>
>> Hi Jon,
>>
>> nothing more than the proposal "To make it clear this is a VOTE by LAZY
>> consensus to use 7.0.0 as next tomee release version." = starting a [VOTE]
>> Apache TomEE 7.0.0 following this vote.
>>
>> "What is GA" - guess you mean more Final since GA just means available and
>> milestone are king of GA by definition? I think it is what the *project*
>> judges stable enough. I think it is very important for us to break this
>> insane dependency to Oracle we don't control and having delayed us of at
>> least 2 years. This means you can see the vote as "is master stable enough
>> to be released as Final and no more as milestone which supposes implicitly
>> no quality guarantee?".
>>
>> Legally we can do Final (0.0) when we want certified or not (TomEE is an
>> autonomous ASF project).
>>
>> If we get TCK and certified we can do a 8.0.0 if you want to "mark" it but
>> that's another topic we'll cover if relevant at that point.
>>
>> Does it clarify the intent?
>>
>> Romain Manni-Bucau
>> @rmannibucau <https://twitter.com/rmannibucau> | Blog
>> <http://rmannibucau.wordpress.com> | Github <
>> https://github.com/rmannibucau> |
>> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
>> <http://www.tomitribe.com> | JavaEE Factory
>> <https://javaeefactory-rmannibucau.rhcloud.com>
>>
>> 2016-04-25 14:28 GMT+02:00 Jonathan Gallimore <jg...@tomitribe.com>:
>>
>> > I'm not sure what I'm voting for and how this relates to the other
>> thread
>> > "Next release 7.1".
>> >
>> > Is it both of the following?
>> >
>> > * No change in version numbering (i.e. continue with 7.0.0.M1, M2, M3,
>> M4
>> > etc until we get to a 7.0.0 GA)
>> > * Include Tomcat 8.5 and later in the 7.0.x series with no separate fork
>> > for Tomcat 8.5 support
>> >
>> > If it is, I'd expect the next release to be a 7.0.0.M4, with Tomcat 8.5
>> > included.
>> >
>> > The next question is - what is GA? As we aligned with Java EE version
>> > numbering, I'd expect a 7.0.0.GA to be a JEE 7 certified released, at
>> > least
>> > for webprofile, and I think it needs to be very clearly communicated if
>> > that is not the case. Are their any legal implications of releasing a
>> TomEE
>> > 7.0.0 GA that is not certified?
>> >
>> > Jon
>> >
>> > On Mon, Apr 25, 2016 at 1:01 PM, Romain Manni-Bucau <
>> rmannibucau@gmail.com
>> > >
>> > 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>
>> > >
>> >
>> >
>> >
>> > --
>> > Jonathan Gallimore
>> > http://twitter.com/jongallimore
>> > http://www.tomitribe.com
>> >
>>
>
>
Re: [VOTE][LAZY] Next tomee release using 7.0.0 version
Posted by Jean-Louis Monteiro <jl...@tomitribe.com>.
Same fear for me. We'll not get any Java EE 7 TCK at Apache. So waiting
only penalize the project.
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com
On Mon, Apr 25, 2016 at 2:39 PM, Romain Manni-Bucau <rm...@gmail.com>
wrote:
> Hi Jon,
>
> nothing more than the proposal "To make it clear this is a VOTE by LAZY
> consensus to use 7.0.0 as next tomee release version." = starting a [VOTE]
> Apache TomEE 7.0.0 following this vote.
>
> "What is GA" - guess you mean more Final since GA just means available and
> milestone are king of GA by definition? I think it is what the *project*
> judges stable enough. I think it is very important for us to break this
> insane dependency to Oracle we don't control and having delayed us of at
> least 2 years. This means you can see the vote as "is master stable enough
> to be released as Final and no more as milestone which supposes implicitly
> no quality guarantee?".
>
> Legally we can do Final (0.0) when we want certified or not (TomEE is an
> autonomous ASF project).
>
> If we get TCK and certified we can do a 8.0.0 if you want to "mark" it but
> that's another topic we'll cover if relevant at that point.
>
> Does it clarify the intent?
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> | Blog
> <http://rmannibucau.wordpress.com> | Github <
> https://github.com/rmannibucau> |
> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> <http://www.tomitribe.com> | JavaEE Factory
> <https://javaeefactory-rmannibucau.rhcloud.com>
>
> 2016-04-25 14:28 GMT+02:00 Jonathan Gallimore <jg...@tomitribe.com>:
>
> > I'm not sure what I'm voting for and how this relates to the other thread
> > "Next release 7.1".
> >
> > Is it both of the following?
> >
> > * No change in version numbering (i.e. continue with 7.0.0.M1, M2, M3, M4
> > etc until we get to a 7.0.0 GA)
> > * Include Tomcat 8.5 and later in the 7.0.x series with no separate fork
> > for Tomcat 8.5 support
> >
> > If it is, I'd expect the next release to be a 7.0.0.M4, with Tomcat 8.5
> > included.
> >
> > The next question is - what is GA? As we aligned with Java EE version
> > numbering, I'd expect a 7.0.0.GA to be a JEE 7 certified released, at
> > least
> > for webprofile, and I think it needs to be very clearly communicated if
> > that is not the case. Are their any legal implications of releasing a
> TomEE
> > 7.0.0 GA that is not certified?
> >
> > Jon
> >
> > On Mon, Apr 25, 2016 at 1:01 PM, Romain Manni-Bucau <
> rmannibucau@gmail.com
> > >
> > 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>
> > >
> >
> >
> >
> > --
> > Jonathan Gallimore
> > http://twitter.com/jongallimore
> > http://www.tomitribe.com
> >
>
Re: [VOTE][LAZY] Next tomee release using 7.0.0 version
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Hi Jon,
nothing more than the proposal "To make it clear this is a VOTE by LAZY
consensus to use 7.0.0 as next tomee release version." = starting a [VOTE]
Apache TomEE 7.0.0 following this vote.
"What is GA" - guess you mean more Final since GA just means available and
milestone are king of GA by definition? I think it is what the *project*
judges stable enough. I think it is very important for us to break this
insane dependency to Oracle we don't control and having delayed us of at
least 2 years. This means you can see the vote as "is master stable enough
to be released as Final and no more as milestone which supposes implicitly
no quality guarantee?".
Legally we can do Final (0.0) when we want certified or not (TomEE is an
autonomous ASF project).
If we get TCK and certified we can do a 8.0.0 if you want to "mark" it but
that's another topic we'll cover if relevant at that point.
Does it clarify the intent?
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>
2016-04-25 14:28 GMT+02:00 Jonathan Gallimore <jg...@tomitribe.com>:
> I'm not sure what I'm voting for and how this relates to the other thread
> "Next release 7.1".
>
> Is it both of the following?
>
> * No change in version numbering (i.e. continue with 7.0.0.M1, M2, M3, M4
> etc until we get to a 7.0.0 GA)
> * Include Tomcat 8.5 and later in the 7.0.x series with no separate fork
> for Tomcat 8.5 support
>
> If it is, I'd expect the next release to be a 7.0.0.M4, with Tomcat 8.5
> included.
>
> The next question is - what is GA? As we aligned with Java EE version
> numbering, I'd expect a 7.0.0.GA to be a JEE 7 certified released, at
> least
> for webprofile, and I think it needs to be very clearly communicated if
> that is not the case. Are their any legal implications of releasing a TomEE
> 7.0.0 GA that is not certified?
>
> Jon
>
> On Mon, Apr 25, 2016 at 1:01 PM, Romain Manni-Bucau <rmannibucau@gmail.com
> >
> 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>
> >
>
>
>
> --
> Jonathan Gallimore
> http://twitter.com/jongallimore
> http://www.tomitribe.com
>
Re: [VOTE][LAZY] Next tomee release using 7.0.0 version
Posted by Jonathan Gallimore <jg...@tomitribe.com>.
I'm not sure what I'm voting for and how this relates to the other thread
"Next release 7.1".
Is it both of the following?
* No change in version numbering (i.e. continue with 7.0.0.M1, M2, M3, M4
etc until we get to a 7.0.0 GA)
* Include Tomcat 8.5 and later in the 7.0.x series with no separate fork
for Tomcat 8.5 support
If it is, I'd expect the next release to be a 7.0.0.M4, with Tomcat 8.5
included.
The next question is - what is GA? As we aligned with Java EE version
numbering, I'd expect a 7.0.0.GA to be a JEE 7 certified released, at least
for webprofile, and I think it needs to be very clearly communicated if
that is not the case. Are their any legal implications of releasing a TomEE
7.0.0 GA that is not certified?
Jon
On Mon, Apr 25, 2016 at 1:01 PM, Romain Manni-Bucau <rm...@gmail.com>
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>
>
--
Jonathan Gallimore
http://twitter.com/jongallimore
http://www.tomitribe.com