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.