[Geoserver-devel] GeoTools / GeoServer Meeting 2016-11-01

Attending


Torben Barsballe
Jody Garnett
Kevin Smith

Actions

  • IanT: email release anouncements to deve/users/discuss/etc… it is a major release

Actions from last meeting:

  • 2.10.0 Release: Bug fixing (done)
  • 2.10.0 Release: Ian / Andrea (done … except for email)

Agenda

  • 2.10.x build failure
  • Commiters
  • Bug Stomp Schedule
  • Release Update
  • Extensions Update

2.10.x build failure

Build failure, not upload ares → repo.boundlessgeo.com “too large”!

Around 100 MB produces this failure.

Why so big? active-mq module for jms-cluster

  • only effecting 2.10.x, not master (huh?)

Q: could an upstream dependency have changed?

  • possible

Q: can we increase the limit at repo.boundlessgeo.com?

  • yes … done. Kicking the build…
  • Build still fails (in the same place), but with a different error:
    [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project activemqBroker: Failed to deploy artifacts: Could not transfer artifact org.geoserver.community:activemqBroker:war:2.10-20161101.201547-1105 from/to boundless (https://repo.boundlessgeo.com/snapshot/)): Connection reset → [Help 1]

Commiters

See email list Nuno Oliveir is nominated for GeoTools commit access!

  • Please respond to email.

Vector tiles has been accepted as an extension, David Blasby has commit access (for this module). Welcome back team GeoServer David.

Thanks to everyone for their help getting the 2.10.0 release out!

Bug Stomp Schedule

1st - propose Nov 18th this month (to avoid holidays)?

2nd - can we provide a set day each month to make scheduling easier?

  • The 18th it tough as it is our monthly release day on the release schedule …
  • Has Friday been working well? Easy to clean up the mess over the weekend
  • But Fridays conflicts with holidays in Nov/Dec.
  • Boundless staff considering joining on Thursday (to avoid meetings)
  • Monday is terrible … recommend Thursday/Friday.

Release Update

The GeoServer 2.10.0 release is out:

The GeoTools blog post may need some love - it is largely a cut and paste of the 2.10-RC1.

We still need to send out emails, adding that as an action item for Ian!

Thanks for the promotion on social media. Jody asked Boundless to cross post.

The macOS installer worked fine - first release in a bit that it has worked with out intervention.

The windows installer story was murder, and a lot of late nights/weekends. We need feedback on installing on windows and “SmartScan”. When we are happy Larry can automate what was a manual process to sign the installer and the application.
Known issues:

  • Uninstaller not signed (terrible workaround it to run the installer, collect the uninstaller, sign, and repackage! Oh NSIS you are terrible…)
  • The wrapper is old, we have an outstanding technical debt to update to a newer one …
  • There is a newer copy of NSIS out we could upgrade to.

Extensions Update

  1. Vector Tiles has graduated to an Extension (GSIP-138)
  • when can we backport to 2.10.x? For inclusion in 2.10.1…
  • usual advise is to wait a month …
  1. Backup and Restore Extension (GSIP-145)
  • waiting on jukka and smithkm to vote
  1. YSLD Extension Status?
  • One blocker in the way, GEOS-7831, the validator does not work when called through the GUI
  • GeoTools extension is not yet ready (lacks docs)
  • Need a GSIP
  1. the resource-gui extension
  • Jody - would like to see this cleaned up and included in main
  • lacks docs (sad) and testing (sadder)

BugStomp Roundup

Quite a busy day on Friday 113 issues closed (17 fixed):

A few ones that got stuck …

  1. GEOS-7752 - default style and wicket/rest restrictions
  • devon got stuck here; discovered GEOS-7828 (which has since been fixed)
  • This issue turns out to also affect the REST API
  1. GEOT-1873 - geotools incubation process open IP issues
  • Simone cheerfully closed this one, general stratagy was to leave it open to express a known issue
  • Jody is writing these into README.md files for each module (and now wants to poke his eyes out)
  1. GEOS-7375 - SLD Upload CDATA whitespace issues
  • Alex was able to reproduce, and hunt down where this occurs in SLDParser, but ran out of time…