As we discussed during 1st Platform TCK call on April 5th, we should try to resolve the technical debt related to legacy Test Vehicles and develop a recipe for Test Vehicles to be used with refactored TCK modules.
IMO, we should sync early next week and come to conclusion on Test Vehicle, which is blocking refactoring of many modules.
We can also discuss on requirement of Test Vehicle in refactored TCK modules, should we continue with Test Vehicles ? or drop Vehicles with refactored TCK?[if test vehicles are not mandate by SPEC or Platform]
regards,
Guru
From: jakartaee-tck-dev <jakartaee-tck-dev-bounces@xxxxxxxxxxx> on behalf of Scott Marlow <smarlow@xxxxxxxxxx> Sent: 06 April 2023 20:15 To: jakartaee-tck developer discussions <jakartaee-tck-dev@xxxxxxxxxxx>; Scott Stark <starksm64@xxxxxxxxx> Subject: Re: [jakartaee-tck-dev] [External] : Re: Platform TCK refactor discussion
There was no consensus on an alternative time, so I suggest having two calls, the first at the normal time with the current agenda, and a second at 5pm GMT-4:00 to discuss the servlet TCK changes by Olivier.
+1 and we can record both calls. I'll mention this in the non-DMARC email thread also.
You are currently receiving this informational message with the original email attached. We need your help in notifying the team or sender responsible for this mail flow to ensure future email is delivered properly.
The host that sent this message is not compliant with Oracle's email security policy (DMARC). Please notify the person(s) responsible for this message and share the content below so they can take actions to resolve their issue.
If you have no idea who is responsible, then please address the #ww-oracle-dmarc slack channel for assistance.
Deadlines
• We plan to move to quarantine non-compliant messages early 2023 (date to be determined). After this date, if the issues are not fixed, messages will be held in a folder on our email gateway and will not be delivered to you.
• We will then move to reject early 2023 (date to be determined). After this date, messages will be rejected.
Maybe we could schedule a separate call to go over the servlet TCK, or even just change the time for the April 5 meeting. Here is a poll for different times:
On Mar 17, 2023 at 9:45:23 PM, Olivier Lamy <olamy@xxxxxxxxxxx> wrote:
I would be happy to participate, especially to talk about the servlet TCK refactoring PR but 11am EST is definitely complicated for my AEST timezone. :(
Based on TCK community feedback on priority
of Platform TCK refactor task and timing constraint of community members due to different time-zone, discussion meetings on TCK refactor can be scheduled much before Platform TCK call on April 5th. Please respond with convenient time for discussion.
