[Geoserver-devel] GeoTools / GeoServer Meeting 2017-01-24

GeoServer GeoServer Developer
1

GeoTools / GeoServer Meeting 2017-01-24

# Attending

Ben Caradoc-Davies

Jody Garnett

Torben Barsballe

Mike Pumphrey

Jukka Rahkonen

Kevin Smith

Reggie Beckwith

Agenda- Sprint Planning / Update

  • Code Freeze Planning

  • YSLD Promotion from Unsupported to Extension (GEOT-5620 / GSIP-154)

  • Catalog Performance Improvements (GSIP-155)

  • Windows Build Box

Actions- Mike to follow up sprint Doodle poll via private email as necessary

  • Torben to look into why Corbertura worked for YSLD, was failing on Java 8 code

  • Everyone please review Catalog Performance Improvements (GSIP-155) (PSC please vote)

  • Ben to send code freeze announcement to mailing list

  • Jody to remind mailing list of bug stomp on Friday

Actions from last meeting- Ian doing the Jan release with some help from Andrea

Sprint Planning / Update

Code sprint:

  • Blog Post

  • http://blog.geoserver.org/2017/01/23/geoserver-code-sprint-2017/

  • Wiki Page (including call for Sponsors)

  • https://wiki.osgeo.org/wiki/FOSS4G_2017_Code_Sprint

  • Finances:

  • Request for OSGeo Funding needed for Feb 2nd OSGeo meeting

  • See Spreadsheet and wiki for details. TLDR: 7500 USD to cover travel, attendees responsible for accommodation (AirBnB or $70 USD a night hotel) and food (bring snacks).

  • Spreadsheet has flight options compared (airport+train)

  • Need help to fill in continental travel details

  • Need help for call out to sponsors

  • If we do not get enough people; we will need to choose a different topic

  • Doodle Poll

  • http://doodle.com/poll/nxti9a3qd5kzeyyb#table

  • Mike has a strong preference for the last week in March

  • Jody is available as indicated in the google poll

  • Waiting for staff from GeoSolutions (our hosts) to weigh in

  • Initial invite was for Feb, but we have pushed back to March

  • Action: Mike to follow up via private email as necessary

 # Code Freeze Planning

Action: (Ben) send reminder to the mail list

Is there anything outstanding before the code freeze:

  • GSIP-154

  • GSIP-155

Release schedule has the beta going out Feb 18th.

  • http://docs.geoserver.org/latest/en/developer/release-schedule/index.html#release-cycle “The hardening phase starts when the second beta is released and continues through all release candidate (RC) releases.“

  • So code Freeze from Feb 18th beta, ands March 3rd RC1 (and creation of the new branch)

  • Feb 18th

  • 2.10.2 - torben volunteers

  • 2.11-beta - jody volunteers

  • Kevin on GWC, torben will shadow

  • March 3rd

  • 2.11-RC1 - a lot more work than usual with new branches and jobs

YSLD Promotion from Unsupported to Extension

See: GEOT-5620 / GSIP-154

Working with Matt on this (he has attended prior bug stomps).

Trying to get this in before the code freeze:

  • YSLD cookbook is now included (thanks torben!)

  • Remember to update the website page download template when adding new extensions (for download and nightly)

  • Most of the work on GeoTools side

  • Improve code - code formatting, please log things, etc…

  • Improved docs

  • Feedback from Kevin/Justin would be useful?

  • Code coverage 70-80% using Cobertura (docs updated for others to run)

  • Action: Torben to look into why Corbertura worked, was failing on Java 8 code.

  • See Cobertura issue #166

  • Others have used EclEmma (Eclipse plugin)

  • Gabriel managed to use different coverage testing tool …

  • Backport to stable? Yes …

Catalog Performance Improvements (GSIP-155)

See: GSIP-155

Darn impressive performance improvement!

Only minor feedback on the pull request so far

Discussion:

  • Concurrent catalog log

  • Reduction in global lock use - this seems like a great idea

Action: please make reviewing this a priority

Windows Build Box

General release stuff, 2.9.4 release.

  • Certificate issue on ares build box:

  • General complete failure on windows build box

  • Prior release was very slow (3 mins → 9 hours slow)

  • Chris / Torben:

  • Running 100% CPU for three months

  • Keep an eye for exe artifacts; email Chris if needed :frowning:

  • Why windows? Makensis is available for linux?

  • https://github.com/geoserver/geoserver/blob/master/build/win_installer.sh

  • Probably for signing things! See discussion with Larry previously …

Bug Stomp

Action: (Jody) Remind mailing list of bug stomp on Friday

Coordinate on mailing list / gitter:

  • Andrea has been tagging some issues as triage

  • Expect some new developers in the mix from boundless

··· 
-- 
Ben Caradoc-Davies [<ben@anonymised.com>](mailto:ben@anonymised.com)
Director
Transient Software Limited [<http://transient.nz/>](http://transient.nz/)
New Zealand
2

I’ve looked into the Cobertura Tests:

Seems to work fine on GeoTools, confirmed it is working on classes that contain Java 8 syntax like lambda expressions.
Looks like GeoServer is currently using a different (earlier) version of Cobertura that produces copious errors. After updating the Cobertura version to match GeoTools (2.7), I got less errors, but still a few.

Notably, it seemed to work fine for simple lambda expressions that only passed a single argument, but failed for lambda expressions that pass multiple arguments (the problem seems to be with the comma delimiting the arguments). For example, the following would fail:

visitChildren(TextField.class, (component, visit) → {
component.setEnabled( !readOnly );
});

From what I can tell, GeoTools just has much less Java 8 syntax than GeoServer, and looks to have none of the syntax that is causing problems with Cobertura.

Even with the errors, coverage reports were still generated. Not sure how accurate those reports were though.

All the information I could find suggests that there has been no new release of Cobertura since February 2015.

Given this, we likely want to look towards switching to a different coverage tool.

Torben

···

On Tue, Jan 24, 2017 at 12:36 PM, Ben Caradoc-Davies <ben@anonymised.com> wrote:

GeoTools / GeoServer Meeting 2017-01-24

# Attending

Ben Caradoc-Davies

Jody Garnett

Torben Barsballe

Mike Pumphrey

Jukka Rahkonen

Kevin Smith

Reggie Beckwith

Agenda- Sprint Planning / Update

  • Code Freeze Planning

  • YSLD Promotion from Unsupported to Extension (GEOT-5620 / GSIP-154)

  • Catalog Performance Improvements (GSIP-155)

  • Windows Build Box

Actions- Mike to follow up sprint Doodle poll via private email as necessary

  • Torben to look into why Corbertura worked for YSLD, was failing on Java 8 code

  • Everyone please review Catalog Performance Improvements (GSIP-155) (PSC please vote)

  • Ben to send code freeze announcement to mailing list

  • Jody to remind mailing list of bug stomp on Friday

Actions from last meeting- Ian doing the Jan release with some help from Andrea

Sprint Planning / Update

Code sprint:

  • Blog Post

  • http://blog.geoserver.org/2017/01/23/geoserver-code-sprint-2017/

  • Wiki Page (including call for Sponsors)

  • https://wiki.osgeo.org/wiki/FOSS4G_2017_Code_Sprint

  • Finances:

  • Request for OSGeo Funding needed for Feb 2nd OSGeo meeting

  • See Spreadsheet and wiki for details. TLDR: 7500 USD to cover travel, attendees responsible for accommodation (AirBnB or $70 USD a night hotel) and food (bring snacks).

  • Spreadsheet has flight options compared (airport+train)

  • Need help to fill in continental travel details

  • Need help for call out to sponsors

  • If we do not get enough people; we will need to choose a different topic

  • Doodle Poll

  • http://doodle.com/poll/nxti9a3qd5kzeyyb#table

  • Mike has a strong preference for the last week in March

  • Jody is available as indicated in the google poll

  • Waiting for staff from GeoSolutions (our hosts) to weigh in

  • Initial invite was for Feb, but we have pushed back to March

  • Action: Mike to follow up via private email as necessary

 # Code Freeze Planning

Action: (Ben) send reminder to the mail list

Is there anything outstanding before the code freeze:

  • GSIP-154

  • GSIP-155

Release schedule has the beta going out Feb 18th.

  • http://docs.geoserver.org/latest/en/developer/release-schedule/index.html#release-cycle “The hardening phase starts when the second beta is released and continues through all release candidate (RC) releases.“

  • So code Freeze from Feb 18th beta, ands March 3rd RC1 (and creation of the new branch)

  • Feb 18th

  • 2.10.2 - torben volunteers

  • 2.11-beta - jody volunteers

  • Kevin on GWC, torben will shadow

  • March 3rd

  • 2.11-RC1 - a lot more work than usual with new branches and jobs

YSLD Promotion from Unsupported to Extension

See: GEOT-5620 / GSIP-154

Working with Matt on this (he has attended prior bug stomps).

Trying to get this in before the code freeze:

  • YSLD cookbook is now included (thanks torben!)

  • Remember to update the website page download template when adding new extensions (for download and nightly)

  • Most of the work on GeoTools side

  • Improve code - code formatting, please log things, etc…

  • Improved docs

  • Feedback from Kevin/Justin would be useful?

  • Code coverage 70-80% using Cobertura (docs updated for others to run)

  • Action: Torben to look into why Corbertura worked, was failing on Java 8 code.

  • See Cobertura issue #166

  • Others have used EclEmma (Eclipse plugin)

  • Gabriel managed to use different coverage testing tool …

  • Backport to stable? Yes …

Catalog Performance Improvements (GSIP-155)

See: GSIP-155

Darn impressive performance improvement!

Only minor feedback on the pull request so far

Discussion:

  • Concurrent catalog log

  • Reduction in global lock use - this seems like a great idea

Action: please make reviewing this a priority

Windows Build Box

General release stuff, 2.9.4 release.

  • Certificate issue on ares build box:

  • General complete failure on windows build box

  • Prior release was very slow (3 mins → 9 hours slow)

  • Chris / Torben:

  • Running 100% CPU for three months

  • Keep an eye for exe artifacts; email Chris if needed :frowning:

  • Why windows? Makensis is available for linux?

  • https://github.com/geoserver/geoserver/blob/master/build/win_installer.sh

  • Probably for signing things! See discussion with Larry previously …

Bug Stomp

Action: (Jody) Remind mailing list of bug stomp on Friday

Coordinate on mailing list / gitter:

  • Andrea has been tagging some issues as triage

  • Expect some new developers in the mix from boundless

-- 
Ben Caradoc-Davies [<ben@anonymised.com>](mailto:ben@anonymised.com)
Director
Transient Software Limited [<http://transient.nz/>](http://transient.nz/)
New Zealand

Check out the vibrant tech community on one of the world’s most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot

Geoserver-devel mailing list
Geoserver-devel@anonymised.com.366…sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

3

On 2017-01-24 4:36 PM, Ben Caradoc-Davies wrote:

Code sprint:

  *

    Blog Post

      o

        http://blog.geoserver.org/2017/01/23/geoserver-code-sprint-2017/

  *

    Wiki Page (including call for Sponsors)

      o

        https://wiki.osgeo.org/wiki/FOSS4G_2017_Code_Sprint

Please update the meeting minutes to use the proper URL for the code sprint: https://wiki.osgeo.org/wiki/Java_2017_Code_Sprint (the original page has been now deleted, as it is reserved for the FOSS4G-Boston code sprint committee's use: https://wiki.osgeo.org/wiki/FOSS4G_2017_Code_Sprint). Sorry for that confusion.

-jeff

--
Jeff McKenna
President Emeritus, OSGeo Foundation
http://wiki.osgeo.org/wiki/Jeff_McKenna

4

Hi Torben,
if you search the archives you’ll see a discussion between me and Gabriel about setting up jacoco.
I did not follow up as it’s really a drag to use…

Cheers
Andrea

···

On Wed, Jan 25, 2017 at 1:32 AM, Torben Barsballe <tbarsballe@anonymised.com> wrote:

I’ve looked into the Cobertura Tests:

Seems to work fine on GeoTools, confirmed it is working on classes that contain Java 8 syntax like lambda expressions.
Looks like GeoServer is currently using a different (earlier) version of Cobertura that produces copious errors. After updating the Cobertura version to match GeoTools (2.7), I got less errors, but still a few.

Notably, it seemed to work fine for simple lambda expressions that only passed a single argument, but failed for lambda expressions that pass multiple arguments (the problem seems to be with the comma delimiting the arguments). For example, the following would fail:

visitChildren(TextField.class, (component, visit) → {
component.setEnabled( !readOnly );
});

From what I can tell, GeoTools just has much less Java 8 syntax than GeoServer, and looks to have none of the syntax that is causing problems with Cobertura.

Even with the errors, coverage reports were still generated. Not sure how accurate those reports were though.

All the information I could find suggests that there has been no new release of Cobertura since February 2015.

Given this, we likely want to look towards switching to a different coverage tool.

Torben

Check out the vibrant tech community on one of the world’s most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot

GeoTools-Devel mailing list
GeoTools-Devel@anonymised.com66…sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

–

On Tue, Jan 24, 2017 at 12:36 PM, Ben Caradoc-Davies <ben@anonymised.com.> wrote:

GeoTools / GeoServer Meeting 2017-01-24

# Attending

Ben Caradoc-Davies

Jody Garnett

Torben Barsballe

Mike Pumphrey

Jukka Rahkonen

Kevin Smith

Reggie Beckwith

Agenda- Sprint Planning / Update

  • Code Freeze Planning

  • YSLD Promotion from Unsupported to Extension (GEOT-5620 / GSIP-154)

  • Catalog Performance Improvements (GSIP-155)

  • Windows Build Box

Actions- Mike to follow up sprint Doodle poll via private email as necessary

  • Torben to look into why Corbertura worked for YSLD, was failing on Java 8 code

  • Everyone please review Catalog Performance Improvements (GSIP-155) (PSC please vote)

  • Ben to send code freeze announcement to mailing list

  • Jody to remind mailing list of bug stomp on Friday

Actions from last meeting- Ian doing the Jan release with some help from Andrea

Sprint Planning / Update

Code sprint:

  • Blog Post

  • http://blog.geoserver.org/2017/01/23/geoserver-code-sprint-2017/

  • Wiki Page (including call for Sponsors)

  • https://wiki.osgeo.org/wiki/FOSS4G_2017_Code_Sprint

  • Finances:

  • Request for OSGeo Funding needed for Feb 2nd OSGeo meeting

  • See Spreadsheet and wiki for details. TLDR: 7500 USD to cover travel, attendees responsible for accommodation (AirBnB or $70 USD a night hotel) and food (bring snacks).

  • Spreadsheet has flight options compared (airport+train)

  • Need help to fill in continental travel details

  • Need help for call out to sponsors

  • If we do not get enough people; we will need to choose a different topic

  • Doodle Poll

  • http://doodle.com/poll/nxti9a3qd5kzeyyb#table

  • Mike has a strong preference for the last week in March

  • Jody is available as indicated in the google poll

  • Waiting for staff from GeoSolutions (our hosts) to weigh in

  • Initial invite was for Feb, but we have pushed back to March

  • Action: Mike to follow up via private email as necessary

 # Code Freeze Planning

Action: (Ben) send reminder to the mail list

Is there anything outstanding before the code freeze:

  • GSIP-154

  • GSIP-155

Release schedule has the beta going out Feb 18th.

  • http://docs.geoserver.org/latest/en/developer/release-schedule/index.html#release-cycle “The hardening phase starts when the second beta is released and continues through all release candidate (RC) releases.“

  • So code Freeze from Feb 18th beta, ands March 3rd RC1 (and creation of the new branch)

  • Feb 18th

  • 2.10.2 - torben volunteers

  • 2.11-beta - jody volunteers

  • Kevin on GWC, torben will shadow

  • March 3rd

  • 2.11-RC1 - a lot more work than usual with new branches and jobs

YSLD Promotion from Unsupported to Extension

See: GEOT-5620 / GSIP-154

Working with Matt on this (he has attended prior bug stomps).

Trying to get this in before the code freeze:

  • YSLD cookbook is now included (thanks torben!)

  • Remember to update the website page download template when adding new extensions (for download and nightly)

  • Most of the work on GeoTools side

  • Improve code - code formatting, please log things, etc…

  • Improved docs

  • Feedback from Kevin/Justin would be useful?

  • Code coverage 70-80% using Cobertura (docs updated for others to run)

  • Action: Torben to look into why Corbertura worked, was failing on Java 8 code.

  • See Cobertura issue #166

  • Others have used EclEmma (Eclipse plugin)

  • Gabriel managed to use different coverage testing tool …

  • Backport to stable? Yes …

Catalog Performance Improvements (GSIP-155)

See: GSIP-155

Darn impressive performance improvement!

Only minor feedback on the pull request so far

Discussion:

  • Concurrent catalog log

  • Reduction in global lock use - this seems like a great idea

Action: please make reviewing this a priority

Windows Build Box

General release stuff, 2.9.4 release.

  • Certificate issue on ares build box:

  • General complete failure on windows build box

  • Prior release was very slow (3 mins → 9 hours slow)

  • Chris / Torben:

  • Running 100% CPU for three months

  • Keep an eye for exe artifacts; email Chris if needed :frowning:

  • Why windows? Makensis is available for linux?

  • https://github.com/geoserver/geoserver/blob/master/build/win_installer.sh

  • Probably for signing things! See discussion with Larry previously …

Bug Stomp

Action: (Jody) Remind mailing list of bug stomp on Friday

Coordinate on mailing list / gitter:

  • Andrea has been tagging some issues as triage

  • Expect some new developers in the mix from boundless

-- 
Ben Caradoc-Davies [<ben@anonymised.com>](mailto:ben@anonymised.com)
Director
Transient Software Limited [<http://transient.nz/>](http://transient.nz/)
New Zealand

Check out the vibrant tech community on one of the world’s most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot

Geoserver-devel mailing list
Geoserver-devel@anonymised.comrge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

==
GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information.

Ing. Andrea Aime

@geowolf
Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
phone: +39 0584 962313

fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.

5

Thanks Jeff, websearch got me. Our meeting notes are sent to the email list … and that it :slight_smile:

So your reply to this thread is enough of a correction.

···

On 25 January 2017 at 05:55, Jeff McKenna <jmckenna@anonymised.com> wrote:

On 2017-01-24 4:36 PM, Ben Caradoc-Davies wrote:

Code sprint:

Blog Post

o

http://blog.geoserver.org/2017/01/23/geoserver-code-sprint-2017/

Wiki Page (including call for Sponsors)

o

https://wiki.osgeo.org/wiki/FOSS4G_2017_Code_Sprint

Please update the meeting minutes to use the proper URL for the code
sprint: https://wiki.osgeo.org/wiki/Java_2017_Code_Sprint (the
original page has been now deleted, as it is reserved for the
FOSS4G-Boston code sprint committee’s use:
https://wiki.osgeo.org/wiki/FOSS4G_2017_Code_Sprint). Sorry for that
confusion.

-jeff

–
Jeff McKenna
President Emeritus, OSGeo Foundation
http://wiki.osgeo.org/wiki/Jeff_McKenna

Check out the vibrant tech community on one of the world’s most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot

Geoserver-devel mailing list
Geoserver-devel@anonymised.com.366…sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

–
Jody Garnett