I am following our procedure for starting a new release candidate, https://docs.geotools.org/latest/developer/procedures/release.html
And the request to maintain prior 24.x and 25.x is causing some conflict ... as we cycle through java11a, java11b, and java11c folders to support independent java 11 builds where geotools / geowebcache and geoserver can share a java 11 local repository. We have the following branches in play: - main /var/jenkins/workspace/java11master - 27.x - new stable branch ??? - 26.x - taking over as maintenance branch /var/jenkins/workspace/java11b - 25.x - should be retired today ... /var/jenkins/workspace/java11a - 24.x - kept active at request of geonode community /var/jenkins/workspace/java11c Holding prior branches open is not that big a deal (they take up disk space, but only a little cpu resources when patches are back ported, and possibly nightly builds). I would like to propose setting up */var/jenkins/workspace/java11_27* for the new 27.x branch so we continue to keep 25.x and 24.x java11 jobs available.... -- Jody Garnett
_______________________________________________ GeoTools-Devel mailing list GeoTools-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
