Jakarta EE is not going to reset back to 1.0. It's going to carry on from where Java EE left off. In fact, the first release of Jakarta EE will be version 8 and will be identical to Java EE 8. Jakarta will then to go version 9, 10, etc.
On Mon, Nov 19, 2018 at 3:56 PM Roberto Cortez <radcor...@yahoo.com.invalid> wrote: > Well that is the thing. > > Some time ago, we aligned TomEE version to be the same as EE. Now, Jakarta > is going to reset the versions back to 1.0 as far as I know, so we don’t > have that link anymore, and we can’t really go back on versions, so I guess > we need to do something like: > > Version x.y.z > > x - major - EE API major change, major Java updates support, arquitectural > changes > y - middle - Changes that don’t fit either on x or z. > z - small - Regular releases, fixes, new features etc. > > What do you think? > > > On 19 Nov 2018, at 21:14, Thomas Andraschko <andraschko.tho...@gmail.com> > wrote: > > > > +1 > > better to use this versioning scheme - and wait for Jakarta EE9 to jump > to > > TomEE9.x > > > > Am Mo., 19. Nov. 2018 um 21:38 Uhr schrieb exabrial12 < > exabr...@gmail.com>: > > > >> What does everyone think about about small releases (8.0.x, 8.1.x, > 8.2.x) > >> with each Minor (middle) number adds a new API? Once we get to all the > >> desired API level we could issue an LTS (so declare that 8.6.x would be > >> like > >> Java11 support, MP, and JEE8, plus it'd be around for awhile). This > sort of > >> models what Java is doing anyway and what Ubuntu has been doing for > >> awhile. > >> > >> I'd rather have a clear, but fast release cadence than the big bang > type of > >> releases we seem to fall into :) Thoughts? > >> > >> > >> > >> -- > >> Sent from: > >> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html > >> > >
