Skip to content

Require Change Logs for Service Releases#902

Open
Pandrex247 wants to merge 1 commit into
jakartaee:masterfrom
Pandrex247:Spec-Committee-83
Open

Require Change Logs for Service Releases#902
Pandrex247 wants to merge 1 commit into
jakartaee:masterfrom
Pandrex247:Spec-Committee-83

Conversation

@Pandrex247
Copy link
Copy Markdown
Contributor

@Pandrex247 Pandrex247 commented May 13, 2026

Follow-up to Spec Committee Issue 83: jakartaee/specification-committee#83

It was raised that there should be a way to see what the difference between the various TCK releases are.
The changelog file mechanism already exists, so this is a draft example of how we may update the format of this file to separate out TCK changes from API changes.

Counterpart to jakartaee/specification-committee#88

@netlify
Copy link
Copy Markdown

netlify Bot commented May 13, 2026

Deploy Preview for jakartaee-specifications ready!

Name Link
🔨 Latest commit 293d18e
🔍 Latest deploy log https://app.netlify.com/projects/jakartaee-specifications/deploys/6a05df1abd2f6500088cd1dd
😎 Deploy Preview https://deploy-preview-902--jakartaee-specifications.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

Signed-off-by: Andrew Pielage <pandrex247@hotmail.com>
@Pandrex247 Pandrex247 force-pushed the Spec-Committee-83 branch from 1d57765 to 293d18e Compare May 14, 2026 14:41
@Pandrex247 Pandrex247 marked this pull request as ready for review May 14, 2026 14:48
@Pandrex247 Pandrex247 changed the title Separate Changelogs for API and TCK Releases Require Change Logs for Service Releases May 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant