[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [jakartaee-tck-dev] Maintenance Release 8.0.3?
|
On 3/3/21 10:34 AM, David Blevins
wrote:
We're at 99% passing with the Web Profile TCK, down to 187
failures. We'll definitely have a handful of challenges
ourselves, so we'd also support (and could even help create) an
8.0.3.
David, that is awesome that TomEE is passing 99%!
Congratulations on the progress ahead! Thanks for volunteering
also for creating the 8.0.3 service release! IMO, we should nail
down the rules a bit more (based on input given in this thread and
from SPEC committee later).
When I did the 9.0.2 service release, I wrote down some notes on
what I did via
https://github.com/eclipse-ee4j/jakartaee-tck/wiki/TCK-Challenge-processing-status.
The notes are brief but they give an outline of the tasks done.
Timing-wise, though, we'd prefer to spend the next
couple weeks focused on 9.1 so we can help validate the optional
ORB changes. We could definitely help with an 8.0.3 afterwards.
It wouldn't be immediately after as there would be some time
needed to talk through the challenges, but hopefully just a few
weeks after. The 9.1 release is likely to be sometime in April,
so perhaps that'd make an 8.0.3 sometime in June.
Olivier, would this timeline work for you? What do
others think?
I think that this is an amazing and timely topic, as when I did
the service releases for EE 9, I questioned what the schedule
really should be. I know some projects that will do multiple
releases in a short period of time to help others. I also know
some projects that will not release more than once a month. My
take away is that we should decide as a community, what the
cadence should be for our TCK service release schedule.
Having said ^ about timeline, the current TCK process does give
some guidelines
https://jakarta.ee/committees/specification/tckprocess:
"
Filing a Challenge
...
* The exact TCK version
...
A consensus that a test produces invalid results will result in
the
exclusion of that test from certification requirements, and an
immediate
update and release of an official distribution of the TCK
including the
new exclude list.
"
I quoted some relevant text above, perhaps there can be different
interpretations of what it means for filing a challenge against
the exact TCK version. I assume that means that challenges are
specific for one exact TCK version. Does that mean we should have
new (Jakarta EE 8 targeted) TCK challenges that duplicate the
accepted (Jakarta EE 9) challenges?
From a timeline perspective, is the `immediate update and release
of an official distribution of the TCK including the new exclude
list` depending on someone to volunteer to do the update/release?
If yes, I think we should ask for a volunteer from TCK committers
that aren't currently on critical path for Jakarta EE 9.1.
Thoughts?
Scott
Hi
Olivier,
Right now, there
were no plans for an 8.0.3 release of the TCK. Not
saying there couldn't
be an 8.0.3 TCK release -- it's just that there were
no plans.
In the past, fixes
to the Java EE TCK were not automatically backported
to previous TCK releases.
Since Java EE didn't have the big breaking change
like we did with
the "jakarta" namespace, it was more straight forward
to just
direct users of the Java EE TCK to the newer versions.
So, this "javax"
to "jakarta" namespace change has definitely
introduced a wrinkle
into the support statements.
We want and need
teams to move forward to the "jakarta" namespace in
Jakarta EE
9. That's where our focus is on maintaining and
enhancing the TCK
bucket. But, we still want to encourage the Jakarta
brand by getting
more TCK compatible implementations -- whether it's
for Jakarta EE 8, or
9, or 9.1...
So, maybe we should
start with that question... What are Webtide's plans
on supporting
Jakarta EE 9? Is Jakarta EE 8 compatibility an "end
game",
or do you have plans to move forward to Jakarta EE 9?
And, the other
question is how many changes are you targeting for
this backport? We
have to weigh the costs of this backporting exercise
along with the release
process against the costs of making progress with 9.1
and beyond -- which
will help with the long-term livelihood of Jakarta.
This is an excellent
discussion point. But, as you can see, there's no
easy answer. :-)
Thanks for raising the question.
---------------------------------------------------
Kevin Sutter
STSM, Jakarta EE and MicroProfile architect @ IBM
e-mail: sutter@xxxxxxxxxx
Twitter: @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)
LinkedIn: https://www.linkedin.com/in/kevinwsutter
Part-time schedule: Tue, Wed, Thu (off on Mon and Fri)
From:
Olivier
Lamy <olamy@xxxxxxxxxxx>
To:
jakartaee-tck
developer discussions <jakartaee-tck-dev@xxxxxxxxxxx>
Date:
03/02/2021
15:58
Subject:
[EXTERNAL]
[jakartaee-tck-dev] Maintenance Release 8.0.3?
Sent
by: "jakartaee-tck-dev"
<jakartaee-tck-dev-bounces@xxxxxxxxxxx>
Hi
Is there any plan to release a 8.0.3?
with some fixes backport? (I'm interested with this
one
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_eclipse-2Dee4j_jakartaee-2Dtck_pull_562&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=R9dtOS3afYnRUmu_zogmh0VnVYl2tse_V7QBUA9yr_4&m=3Vb3-CGoObTzZTnNFtk0F2FwehNBDTUdSoYJEXN0n9M&s=FS9b-MBCGKcjlC0P2GC6RlzHvQBlQ6XIWDn694WzBqY&e= )
and maybe more?
cheers
--
Olivier
_______________________________________________
jakartaee-tck-dev mailing list
jakartaee-tck-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev
_______________________________________________
jakartaee-tck-dev mailing list
jakartaee-tck-dev@xxxxxxxxxxx
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev
_______________________________________________
jakartaee-tck-dev mailing list
jakartaee-tck-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev