[Geoserver-devel] Release of 23.0/1/17.0/2.17.0 begining

I’m kicking off the release chain using

GeoServer 6549c85312853ecb22b51d258423c983f22617cd
GeoWebCache - a31bcff2bd98e40c2dc5d176efe3b64b38d11429
GeoTools - 9dca3294fe372826163e25e46a3a1ae7a26a8684

I’ll keep people informed on the lists as I go, I expect to have artifacts ready to test this afternoon for GeoTools.

Ian

···

Ian Turton

I see, Ian please be aware that the deployment repositories have changed :slight_smile:

I did not get a chance to address the package issues for GeoServer mentioned on email.

···


Jody Garnett

I see, Ian please be aware that the deployment repositories have changed :slight_smile:

So, do I need to update the release scripts? or has that been done?

I did not get a chance to address the package issues for GeoServer mentioned on email.

Which ones were those?

Ian

···

Ian Turton

Just focusing on geoserver-devel here:

The email “2.17-RC available for testing” has the details, but TLDR:

  1. build_release.sh failed to find the assembly (and used its fallback plan for older branches which does not include api folder)
  2. Several extension bundles to fix, notably geoserver-2.17-RC-control-flow-plugin.zip
  3. Deployed gs-web-app.jar is too big due to build order and failure to filter
···


Jody Garnett

Ian the following PR addresses these concerns: https://github.com/geoserver/geoserver/pull/4186

I have isolated some community modules into profiles, including the gs-script-py module (which is now off by default as theSNAPSHOT required is no longer published anywhere after the repository change).


Jody Garnett

On Thu, 9 Apr 2020 at 17:14, Jody Garnett <jody.garnett@anonymised.com> wrote:

Just focusing on geoserver-devel here:

The email “2.17-RC available for testing” has the details, but TLDR:

  1. build_release.sh failed to find the assembly (and used its fallback plan for older branches which does not include api folder)
  2. Several extension bundles to fix, notably geoserver-2.17-RC-control-flow-plugin.zip
  3. Deployed gs-web-app.jar is too big due to build order and failure to filter


Jody Garnett

On Thu, 9 Apr 2020 at 07:25, Ian Turton <ijturton@anonymised.com> wrote:

On Thu, 9 Apr 2020 at 15:01, Jody Garnett <jody.garnett@…403…> wrote:

I see, Ian please be aware that the deployment repositories have changed :slight_smile:

So, do I need to update the release scripts? or has that been done?

I did not get a chance to address the package issues for GeoServer mentioned on email.

Which ones were those?

Ian


Jody

On Thu, Apr 9, 2020 at 2:58 AM Ian Turton <ijturton@anonymised.com> wrote:

I’m kicking off the release chain using

GeoServer 6549c85312853ecb22b51d258423c983f22617cd
GeoWebCache - a31bcff2bd98e40c2dc5d176efe3b64b38d11429
GeoTools - 9dca3294fe372826163e25e46a3a1ae7a26a8684

I’ll keep people informed on the lists as I go, I expect to have artifacts ready to test this afternoon for GeoTools.

Ian

Ian Turton


Geowebcache-devel mailing list
Geowebcache-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geowebcache-devel


Jody Garnett

Ian Turton