You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomee.apache.org by Jean-Louis Monteiro <jl...@tomitribe.com> on 2022/02/28 09:22:13 UTC
[VOTE] Apache TomEE - Jakarta EE API 9.1.1
Hi All,
This is a first attempt at a vote for a release of Apache TomEE /
jakartaee-api 9.1.1.
This is essentially the first milestone of the Jakarta EE 9 APIs using the
new jakarta namespace. It's probably going to move a bit and lead to
another set of releases to refine it.
Maven Repo:
https://repository.apache.org/content/repositories/orgapachetomee-1194
Binaries & Source:
https://dist.apache.org/repos/dist/dev/tomee/jakartaee-api_staging-1194/
Tags:
https://github.com/apache/tomee-jakartaee-api/tree/jakartaee-api-9.1.1
Please VOTE:
[+1] Yes, release it
[+0] Not fussed
[-1] Don't release, there's a showstopper (please specify what the
showstopper is)
Vote will be open for 72 hours.
Thanks
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com
[CANCEL] [VOTE] Apache TomEE - Jakarta EE API 9.1.1
Posted by Jean-Louis Monteiro <jl...@tomitribe.com>.
Cancelling this one so I can start another one.
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com
On Mon, Feb 28, 2022 at 10:56 PM David Blevins <db...@tomitribe.com>
wrote:
> Awesome. Let’s use Richard’s suggestion of continuing to put our version
> number after a dash, i.e. 9.1.0-x (9.1.0-M1).
>
> On the Jakarta side the spec process does define all three digits, the
> third being a service release. So there very well could be a Jakarta EE
> x.y.z release.
>
> We’re also a little fast and loose with the rules on the Jakarta side, so
> while service releases shouldn’t have behavior changes, everyone decided
> adding module-info.java files in service releases was ok.
>
> If we also used the third digit there could be a conflict and/or be
> misleading to people as to why the digits are different. Similarly, we’re
> probably smart to always add the third digit exactly as it exists on the
> Jakarta side.
>
>
> -David
>
> On Mon, Feb 28, 2022 at 3:05 PM Jean-Louis Monteiro <
> jlmonteiro@tomitribe.com> wrote:
>
> > Il fine to re roll.
> > I'll do that tomorrow morning
> >
> > Le lun. 28 févr. 2022 à 16:37, Zowalla, Richard <
> > richard.zowalla@hs-heilbronn.de> a écrit :
> >
> > > Another option would be to stay with the same schema as for the EE8 API
> > > Jar, which was: 8.0-x (x keeps incrementing). Would be somehow
> > > consistent but that scheme could be the case after 9.1 has passed the
> > > TCK.
> > >
> > > So I am fine with David's proposal.
> > >
> > > Gruß
> > > Richard
> > >
> > > Am Montag, dem 28.02.2022 um 04:41 -0500 schrieb David Blevins:
> > > > Is it possible we can reroll and use a milestone version, like 9.1.0-
> > > > M1 or similar?
> > > >
> > > > My concern is we haven't yet passed the TCK with this new version and
> > > > if we keep incrementing from here there'll be a point were say (for
> > > > example) 9.1.4 and before haven't passed the tck and 9.1.5 and after
> > > > have passed the TCK and users will have no way of knowing which
> > > > without reading docs.
> > > >
> > > > It'd be better if we used some sort of -M1, -M2, -M3 or -alpha-1, or
> > > > -beta-1 suffix until we've passed the TCK again and know we have a
> > > > jar that's compliant.
> > > >
> > > >
> > > > -David
> > > >
> > > >
> > > > > On Feb 28, 2022, at 4:22 AM, Jean-Louis Monteiro <
> > > > > jlmonteiro@tomitribe.com> wrote:
> > > > >
> > > > > Hi All,
> > > > >
> > > > > This is a first attempt at a vote for a release of Apache TomEE /
> > > > > jakartaee-api 9.1.1.
> > > > > This is essentially the first milestone of the Jakarta EE 9 APIs
> > > > > using the
> > > > > new jakarta namespace. It's probably going to move a bit and lead
> > > > > to
> > > > > another set of releases to refine it.
> > > > >
> > > > > Maven Repo:
> > > > >
> > https://repository.apache.org/content/repositories/orgapachetomee-1194
> > > > >
> > > > > Binaries & Source:
> > > > >
> > >
> https://dist.apache.org/repos/dist/dev/tomee/jakartaee-api_staging-1194/
> > > > >
> > > > > Tags:
> > > > >
> > https://github.com/apache/tomee-jakartaee-api/tree/jakartaee-api-9.1.1
> > > > >
> > > > > Please VOTE:
> > > > >
> > > > > [+1] Yes, release it
> > > > > [+0] Not fussed
> > > > > [-1] Don't release, there's a showstopper (please specify what the
> > > > > showstopper is)
> > > > >
> > > > > Vote will be open for 72 hours.
> > > > >
> > > > > Thanks
> > > > > --
> > > > > Jean-Louis Monteiro
> > > > > http://twitter.com/jlouismonteiro
> > > > > http://www.tomitribe.com
> > >
> >
> --
> Sent from Gmail Mobile
>
Re: [VOTE] Apache TomEE - Jakarta EE API 9.1.1
Posted by David Blevins <db...@tomitribe.com>.
Awesome. Let’s use Richard’s suggestion of continuing to put our version
number after a dash, i.e. 9.1.0-x (9.1.0-M1).
On the Jakarta side the spec process does define all three digits, the
third being a service release. So there very well could be a Jakarta EE
x.y.z release.
We’re also a little fast and loose with the rules on the Jakarta side, so
while service releases shouldn’t have behavior changes, everyone decided
adding module-info.java files in service releases was ok.
If we also used the third digit there could be a conflict and/or be
misleading to people as to why the digits are different. Similarly, we’re
probably smart to always add the third digit exactly as it exists on the
Jakarta side.
-David
On Mon, Feb 28, 2022 at 3:05 PM Jean-Louis Monteiro <
jlmonteiro@tomitribe.com> wrote:
> Il fine to re roll.
> I'll do that tomorrow morning
>
> Le lun. 28 févr. 2022 à 16:37, Zowalla, Richard <
> richard.zowalla@hs-heilbronn.de> a écrit :
>
> > Another option would be to stay with the same schema as for the EE8 API
> > Jar, which was: 8.0-x (x keeps incrementing). Would be somehow
> > consistent but that scheme could be the case after 9.1 has passed the
> > TCK.
> >
> > So I am fine with David's proposal.
> >
> > Gruß
> > Richard
> >
> > Am Montag, dem 28.02.2022 um 04:41 -0500 schrieb David Blevins:
> > > Is it possible we can reroll and use a milestone version, like 9.1.0-
> > > M1 or similar?
> > >
> > > My concern is we haven't yet passed the TCK with this new version and
> > > if we keep incrementing from here there'll be a point were say (for
> > > example) 9.1.4 and before haven't passed the tck and 9.1.5 and after
> > > have passed the TCK and users will have no way of knowing which
> > > without reading docs.
> > >
> > > It'd be better if we used some sort of -M1, -M2, -M3 or -alpha-1, or
> > > -beta-1 suffix until we've passed the TCK again and know we have a
> > > jar that's compliant.
> > >
> > >
> > > -David
> > >
> > >
> > > > On Feb 28, 2022, at 4:22 AM, Jean-Louis Monteiro <
> > > > jlmonteiro@tomitribe.com> wrote:
> > > >
> > > > Hi All,
> > > >
> > > > This is a first attempt at a vote for a release of Apache TomEE /
> > > > jakartaee-api 9.1.1.
> > > > This is essentially the first milestone of the Jakarta EE 9 APIs
> > > > using the
> > > > new jakarta namespace. It's probably going to move a bit and lead
> > > > to
> > > > another set of releases to refine it.
> > > >
> > > > Maven Repo:
> > > >
> https://repository.apache.org/content/repositories/orgapachetomee-1194
> > > >
> > > > Binaries & Source:
> > > >
> > https://dist.apache.org/repos/dist/dev/tomee/jakartaee-api_staging-1194/
> > > >
> > > > Tags:
> > > >
> https://github.com/apache/tomee-jakartaee-api/tree/jakartaee-api-9.1.1
> > > >
> > > > Please VOTE:
> > > >
> > > > [+1] Yes, release it
> > > > [+0] Not fussed
> > > > [-1] Don't release, there's a showstopper (please specify what the
> > > > showstopper is)
> > > >
> > > > Vote will be open for 72 hours.
> > > >
> > > > Thanks
> > > > --
> > > > Jean-Louis Monteiro
> > > > http://twitter.com/jlouismonteiro
> > > > http://www.tomitribe.com
> >
>
--
Sent from Gmail Mobile
Re: [VOTE] Apache TomEE - Jakarta EE API 9.1.1
Posted by Jean-Louis Monteiro <jl...@tomitribe.com>.
Il fine to re roll.
I'll do that tomorrow morning
Le lun. 28 févr. 2022 à 16:37, Zowalla, Richard <
richard.zowalla@hs-heilbronn.de> a écrit :
> Another option would be to stay with the same schema as for the EE8 API
> Jar, which was: 8.0-x (x keeps incrementing). Would be somehow
> consistent but that scheme could be the case after 9.1 has passed the
> TCK.
>
> So I am fine with David's proposal.
>
> Gruß
> Richard
>
> Am Montag, dem 28.02.2022 um 04:41 -0500 schrieb David Blevins:
> > Is it possible we can reroll and use a milestone version, like 9.1.0-
> > M1 or similar?
> >
> > My concern is we haven't yet passed the TCK with this new version and
> > if we keep incrementing from here there'll be a point were say (for
> > example) 9.1.4 and before haven't passed the tck and 9.1.5 and after
> > have passed the TCK and users will have no way of knowing which
> > without reading docs.
> >
> > It'd be better if we used some sort of -M1, -M2, -M3 or -alpha-1, or
> > -beta-1 suffix until we've passed the TCK again and know we have a
> > jar that's compliant.
> >
> >
> > -David
> >
> >
> > > On Feb 28, 2022, at 4:22 AM, Jean-Louis Monteiro <
> > > jlmonteiro@tomitribe.com> wrote:
> > >
> > > Hi All,
> > >
> > > This is a first attempt at a vote for a release of Apache TomEE /
> > > jakartaee-api 9.1.1.
> > > This is essentially the first milestone of the Jakarta EE 9 APIs
> > > using the
> > > new jakarta namespace. It's probably going to move a bit and lead
> > > to
> > > another set of releases to refine it.
> > >
> > > Maven Repo:
> > > https://repository.apache.org/content/repositories/orgapachetomee-1194
> > >
> > > Binaries & Source:
> > >
> https://dist.apache.org/repos/dist/dev/tomee/jakartaee-api_staging-1194/
> > >
> > > Tags:
> > > https://github.com/apache/tomee-jakartaee-api/tree/jakartaee-api-9.1.1
> > >
> > > Please VOTE:
> > >
> > > [+1] Yes, release it
> > > [+0] Not fussed
> > > [-1] Don't release, there's a showstopper (please specify what the
> > > showstopper is)
> > >
> > > Vote will be open for 72 hours.
> > >
> > > Thanks
> > > --
> > > Jean-Louis Monteiro
> > > http://twitter.com/jlouismonteiro
> > > http://www.tomitribe.com
>
Re: [VOTE] Apache TomEE - Jakarta EE API 9.1.1
Posted by "Zowalla, Richard" <ri...@hs-heilbronn.de>.
Another option would be to stay with the same schema as for the EE8 API
Jar, which was: 8.0-x (x keeps incrementing). Would be somehow
consistent but that scheme could be the case after 9.1 has passed the
TCK.
So I am fine with David's proposal.
Gruß
Richard
Am Montag, dem 28.02.2022 um 04:41 -0500 schrieb David Blevins:
> Is it possible we can reroll and use a milestone version, like 9.1.0-
> M1 or similar?
>
> My concern is we haven't yet passed the TCK with this new version and
> if we keep incrementing from here there'll be a point were say (for
> example) 9.1.4 and before haven't passed the tck and 9.1.5 and after
> have passed the TCK and users will have no way of knowing which
> without reading docs.
>
> It'd be better if we used some sort of -M1, -M2, -M3 or -alpha-1, or
> -beta-1 suffix until we've passed the TCK again and know we have a
> jar that's compliant.
>
>
> -David
>
>
> > On Feb 28, 2022, at 4:22 AM, Jean-Louis Monteiro <
> > jlmonteiro@tomitribe.com> wrote:
> >
> > Hi All,
> >
> > This is a first attempt at a vote for a release of Apache TomEE /
> > jakartaee-api 9.1.1.
> > This is essentially the first milestone of the Jakarta EE 9 APIs
> > using the
> > new jakarta namespace. It's probably going to move a bit and lead
> > to
> > another set of releases to refine it.
> >
> > Maven Repo:
> > https://repository.apache.org/content/repositories/orgapachetomee-1194
> >
> > Binaries & Source:
> > https://dist.apache.org/repos/dist/dev/tomee/jakartaee-api_staging-1194/
> >
> > Tags:
> > https://github.com/apache/tomee-jakartaee-api/tree/jakartaee-api-9.1.1
> >
> > Please VOTE:
> >
> > [+1] Yes, release it
> > [+0] Not fussed
> > [-1] Don't release, there's a showstopper (please specify what the
> > showstopper is)
> >
> > Vote will be open for 72 hours.
> >
> > Thanks
> > --
> > Jean-Louis Monteiro
> > http://twitter.com/jlouismonteiro
> > http://www.tomitribe.com
Re: [VOTE] Apache TomEE - Jakarta EE API 9.1.1
Posted by David Blevins <da...@gmail.com>.
Is it possible we can reroll and use a milestone version, like 9.1.0-M1 or similar?
My concern is we haven't yet passed the TCK with this new version and if we keep incrementing from here there'll be a point were say (for example) 9.1.4 and before haven't passed the tck and 9.1.5 and after have passed the TCK and users will have no way of knowing which without reading docs.
It'd be better if we used some sort of -M1, -M2, -M3 or -alpha-1, or -beta-1 suffix until we've passed the TCK again and know we have a jar that's compliant.
-David
> On Feb 28, 2022, at 4:22 AM, Jean-Louis Monteiro <jl...@tomitribe.com> wrote:
>
> Hi All,
>
> This is a first attempt at a vote for a release of Apache TomEE /
> jakartaee-api 9.1.1.
> This is essentially the first milestone of the Jakarta EE 9 APIs using the
> new jakarta namespace. It's probably going to move a bit and lead to
> another set of releases to refine it.
>
> Maven Repo:
> https://repository.apache.org/content/repositories/orgapachetomee-1194
>
> Binaries & Source:
> https://dist.apache.org/repos/dist/dev/tomee/jakartaee-api_staging-1194/
>
> Tags:
> https://github.com/apache/tomee-jakartaee-api/tree/jakartaee-api-9.1.1
>
> Please VOTE:
>
> [+1] Yes, release it
> [+0] Not fussed
> [-1] Don't release, there's a showstopper (please specify what the
> showstopper is)
>
> Vote will be open for 72 hours.
>
> Thanks
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com