yep i think we have to maintain 8.0.x anyway as its the last javax release and we cant expect that everyone does a fast migration
IMO the following is the best way: - branch 8.0.x - make master 9.0 and rename javax -> jakarta - branch 9.0 after everything is working fine - working on 10.0 in master - maintain 8.0 and 10.0 and dont maintain the 9.0 branch Am Di., 5. Okt. 2021 um 10:53 Uhr schrieb Jean-Louis Monteiro < [email protected]>: > Agreed ... > > 1.7.x - EOL > 7.0.x and 7.1.x - mostly similar so if we maintain one, we should maintain > the other. > > But I agree that 1 actively developed version (TomEE master/TomEE 9.x) and > 1 maintained version (TomEE 8.x) is good. > That'd be my choice. > -- > Jean-Louis Monteiro > http://twitter.com/jlouismonteiro > http://www.tomitribe.com > > > On Tue, Oct 5, 2021 at 10:37 AM Zowalla, Richard < > [email protected]> wrote: > > > +1 > > > > I am wondering, if we still maintain 7.0.x, 7.1.x in the future (1.7.x > > is eol, I guess) ? Maintenance cost will rise with every additional > > version branch. The last releases of 7.0.x and 7.1.x are 1 year old... > > but this is maybe another discussion. > > > > > > Am Dienstag, dem 05.10.2021 um 10:05 +0200 schrieb Jean-Louis Monteiro: > > > Thanks everyone. > > > > > > Same feeling here. > > > I think we tried and pushed it as much as we could. > > > > > > What we can do is make sure we fix remaining failures on TCK and > > > support > > > JDK 17 with TomEE. > > > Do a release, branch for maintenance and move master to jakarta. > > > > > > Does it sound like an acceptable plan? > > > > > > -- > > > Jean-Louis Monteiro > > > http://twitter.com/jlouismonteiro > > > http://www.tomitribe.com > > > > > > > > > On Tue, Oct 5, 2021 at 7:56 AM David Jencks <[email protected] > > > > > > > wrote: > > > > > > > Maybe even “Our second release _confirmed_…”… > > > > > > > > David Jencks > > > > > > > > > On Oct 4, 2021, at 12:33 PM, David Blevins < > > > > > [email protected]> > > > > wrote: > > > > > > - Our first release proved releasing both 8 & 9 together can be > > > > impractical. The TomEE 8 binaries were a dud, only TomEE 9 was > > > > released. > > > > There was communication overhead and made for a potentially > > > > confusing > > > > release. The TomEE 9 binaries are still very limited. > > > > > > - Our first release proved releasing both 8 & 9 together can be > > > > impractical. The TomEE 8 binaries were released, we didn't release > > > > TomEE > > > > 9. It's the second time we've done that. We've only managed one > > > > TomEE 9 > > > > release in the last 10 months. > > > > > This was supposed to start "our second > > > > > release". CopyPasteException :) > > > > > > > > > > -David > > > > > > > -- > > Richard Zowalla, M.Sc. > > Research Associate, PhD Student | Medical Informatics > > > > Hochschule Heilbronn – University of Applied Sciences > > Max-Planck-Str. 39 > > D-74081 Heilbronn > > phone: +49 7131 504 6791 (zur Zeit nicht via Telefon erreichbar) > > mail: [email protected] > > web: https://www.mi.hs-heilbronn.de/ > > >
