Branch Git repositories for Java 17 platform

Description

Now that we have proof-of-concept code for the Java 17 platform, the next step, as determined on the call, is to start branching the Git repositories for components as they move across to new development.

The general convention we have used before is to create a maint-MAJOR branch (e.g., maint-11, maint-4, etc.), switch Jenkins and developer references across to that, and have the new development occur on main. In this case, we have a preliminary branch we want to merge into main before that will be complete.

Environment

None

Activity

Ian YoungMay 30, 2022 at 3:02 PM
Edited

I have landed the development branches, so these same five repositories are now open for v5 development. Jenkins has been adjusted.

Next up:

  • Nightly and Multi job sets for these repositories

  • Ferret out signing keys for the new dependencies.

  • Figure out which other repositories we need to branch.

Ian YoungMay 26, 2022 at 11:06 AM

Next up: for the same set of repositories, reviewing and landing the various development branches and landing an appropriate set of changes to main, and switching the v17 view jobs over to main.

Ian YoungMay 26, 2022 at 11:05 AM

The following repositories have been branched:

  • java-parent-project branched to maint-11

  • java-support branched to maint-8

  • spring-extensions branched to maint-6

  • java-opensaml branched to maint-4

  • java-identity-provider branched to maint-4

I have adjusted all the appropriate Jenkins jobs (in the v11, v11-multi, v11-nightly and v11-site views) to point to the appropriate maintenance branches.

I will send mail to the dev list letting people know this has happened.

Done

Details

Assignee

Reporter

Fix versions

Affects versions

Created May 26, 2022 at 10:35 AM
Updated July 27, 2022 at 3:19 PM
Resolved July 27, 2022 at 3:19 PM