I am having a small amount of luck, eventually getting the build server to make a milestone release:
- https://build.geoserver.org/view/release/job/geoserver-release/68/artifact/distribution/2.21-M0/ Feedback welcome. -- Jody Garnett On Apr 20, 2022 at 6:16:11 PM, Jody Garnett <jody.garn...@gmail.com> wrote: > With everyone busy, I thought I would try and make a 2.21-M0 milestone > release (as I would like public feedback from log4j branch and I understand > it is a large pull request to review). > The procedure to do so asks the build_release.sh script to build geotools > and geowebcache commits, and that functionality has not been tried out for > some time.... > > > - Reduced branch to four commits and pushed up to > https://github.com/geoserver/geoserver/tree/log4j2_upgrade > - New pull request is https://github.com/geoserver/geoserver/pull/5823 from > the above branch > - build_release.sh requires a release in jira, 2.21-M0 release notes > are here: > > https://osgeo-org.atlassian.net/secure/ReleaseNote.jspa?projectId=10000&version=16851 > > - The ticket https://osgeo-org.atlassian.net/browse/GEOS-10426 can be > marked as fixed for 2.21-M0 and 2.21-RC so it does not miss out on future > release notes > - GitHub policy has changed, build_release.sh was trying to use git: > protocol anonymously to checkout geotools and geowebcache which is no > longer allowed. Changing to HTTPS protocol seems to work > - Presently this has gotten as far as ... gt-metadata integration > tests (sigh) which I will troubleshoot on geotools-devel > > > If all goes well I can publish a milestone release source forge for public > feedback, and provide an update for activity sponsors. > -- > Jody Garnett >
_______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
