Vote: Should api/spec and tck/tck-dist have diverging service releases?

[KyleAure]

Description

For service release #762 we have changes to the TCK and TCK distribution modules that need a service release.
There are no changes to the api or spec modules (except for plugin dependency updates)

Arguments

For divergence

• Possibility to do more frequent service releases for TCK changes.

Against divergence

• We would need to update our build process (Jenkins jobs) to allow for this type of release structure
• We would would have to create more complex GitHub branches (ex. RELEASE-API-1.0.0-TCK-1.1.0)
• Diverging releases would naturally lead to the question "Why not put the TCK into it's own project?" which would mean API and TCK changes would no longer be able to be made in parallel

Voting options

👍🏼 : Diverge service releases -- api and spec will stay at 1.0.0 and tck and tck-dist will be released at 1.0.1
👎🏼 : Keep parallel service releases -- api, spec, tck, and tck-dist will be released at 1.0.1

Voting Process

1. If you have any other for/against arguments to be made please comment them below.
   • I will add them to the running argument list
2. Vote by reacting to this issue with either a 👍🏼 (for) or 👎🏼 (against) vote
3. Voting will end in 1 week : June 18th 2024 @ 12:00PM CDT

[KyleAure]

Closing vote:
3 : 👎🏼 : Keep parallel service releases
0 : 👍🏼 : Diverge service releases