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 <
> > jlmonte...@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

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to