>
> 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
+1
In terms of how we handle 9.x, I think we'd want to
> On Oct 5, 2021, at 1:59 AM, Thomas Andraschko
> wrote:
>
> 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 -> jaka
Hi all,
the proposed plan by Thomas sounds reasonable. +1
IMHO, 8.0.x line should definitely be continued for those not able to migrate
yet, as brought up by Jean-Louis.
Given the planned 8.0.9 version will compatible and work with Java 17 (LTS),
that 8.0.x line should be curated for some time.
Thanks for the additional thoughts Thomas.
I'll wait for some more thoughts and I might create a poll and let everyone
to vote on what they like.
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com
On Tue, Oct 5, 2021 at 10:59 AM Thomas Andraschko <
andraschko.tho..
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 maste
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/jlouismo
+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 s
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-Lou
Maybe even “Our second release _confirmed_…”…
David Jencks
> On Oct 4, 2021, at 12:33 PM, David Blevins 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
> - 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
> On Oct 1, 2021, at 4:25 AM, Jean-Louis Monteiro
> wrote:
>
> I was about to add that into tomee-jakarta by having the same approach so
> we don't have the cost of maintaining both TomEE 8 and TomEE source tree.
>
> But looks like to do that we end up by duplicating pretty much the entire
> To
It's a bit of a chicken and the egg issue.
We could target EE 9 as well. The point is we have to duplicate a lot of
modules from master to tomee-jakarta project and configure the transformer
to do package relocation.
Works but quite heavy if we want to cover everything.
If we decide to move maste
I agree with Thomas.
We are not migrating to EE9 (with TomEE) as we are missing the plugins,
unit-test containers, arquillian integration, etc. - I guess, the next
one will be EE10 to aim for.
Gruss
Richard
Am Freitag, dem 01.10.2021 um 13:40 +0200 schrieb Thomas Andraschko:
> TBH we have to mi
On Fri, Oct 1, 2021 at 1:40 PM Thomas Andraschko <
andraschko.tho...@gmail.com> wrote:
> TBH we have to migrate to jakarta anyway. Targeting EE9 or EE10.
>
That's my point. We'll have to do it someday.
>
> IMO the most people dont care about EE9, so i would branch/tag EE9 on the
> road to EE10
TBH we have to migrate to jakarta anyway. Targeting EE9 or EE10.
IMO the most people dont care about EE9, so i would branch/tag EE9 on the
road to EE10 but never maintain or release it.
Also not sure about the exact timeline, when we should start to migrate.
Am Fr., 1. Okt. 2021 um 13:25 Uhr
Hi all,
I was looking at a way to do a final release of TomEE 9 but we have some
significant work before we can do that.
- arquillian integration
- standalone and lite distributions
- Maven plugins
- boms
I was about to add that into tomee-jakarta by having the same approach so
we don't have the
16 matches
Mail list logo
