Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[jakartaee-platform-dev] Platform releases, tags, and branches in github repos

This topic is specific to the repositories that are used to deliver the Jakarta EE Platform (jakartaee-platform, jakartaee-api, and jakartaee-schemas).  This is communicating what we're doing.  It's not meant as a directive or even a suggestion to the other Projects and their repositories.  These questions were raised while cleaning up some "old" Issues and PRs in our repos.  We thought it would be good to communicate to the wider Platform team.

When a release is performed in github, we have the Release and Tag pointing at a specific commit (ie.  If at a later point in time, a maintenance release is required, we can go back to this commit level and create a new branch for doing the necessary updates and subsequent release.  There is no requirement to pre-create a branch for maintenance -- create when needed.

In the case of jakartaee-api, it looks like there are some maintenance issues that need addressing.  In that repo, we do have the 8.0.0-BRANCH branch.  The pom was recently updated to correctly indicate the version for this branch is 8.0.1-SNAPSHOT.  This gives us the proper location for maintenance efforts on the API in case we need to do an 8.0.1 release down the road (or 8.0.n).

Pretty straight forward.  Just wanted everyone to know the direction we've been taking with the maintenance path.

Kevin Sutter
STSM, MicroProfile and Jakarta EE architect @ IBM
e-mail:  sutter@xxxxxxxxxx     Twitter:  @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)    

Back to the top