[cu-dev] Vote: Should api/spec and tck/tck-dist have diverging service r

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[cu-dev] Vote: Should api/spec and tck/tck-dist have diverging service releases?

From: Kyle Aure <kylejaure@xxxxxxxxx>
Date: Tue, 11 Jun 2024 11:56:16 -0500
Delivered-to: cu-dev@xxxxxxxxxxx
List-archive: <https://www.eclipse.org/mailman/private/cu-dev/>
List-help: <mailto:cu-dev-request@eclipse.org?subject=help>
List-subscribe: <https://www.eclipse.org/mailman/listinfo/cu-dev>, <mailto:cu-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://www.eclipse.org/mailman/options/cu-dev>, <mailto:cu-dev-request@eclipse.org?subject=unsubscribe>

Hello Everyone,

A question was brought up today on the Platform call about how service releases should be handled when only updating the TCK.

The guidance from the Platform call was that it is up to each specification to decide how they handle these services releases.

I have opened a vote for this issue here: https://github.com/jakartaee/concurrency/issues/526

Voting closes June 18th 2024 @ 12:00PM CDT

Thank you,

Kyle Jon Aure

Prev by Date: [cu-dev] Concurrency 3.1 Ballot Successful!
Next by Date: [cu-dev] Concurrency 3.0 TCK test failures in ManagedScheduledExecutorDefinitionTests.testScheduleWithCronTrigger
Previous by thread: [cu-dev] Concurrency 3.1 Ballot Successful!
Next by thread: [cu-dev] Concurrency 3.0 TCK test failures in ManagedScheduledExecutorDefinitionTests.testScheduleWithCronTrigger
Index(es):
- Date
- Thread

Back to the top