[Geoserver-devel] GeoServer 2.16.1 release train reminder

GeoServer GeoServer Developer
1

The GeoServer 2.16.2 release is scheduled for this week. If you have any fixes or pull requests this is your reminder :slight_smile:

···

–
Jody Garnett

2

Reminder 2, 2.16.1 is a stable series release, so careful about what you backport

only a few days before the release

Cheers
Andrea

···

Regards, Andrea Aime == 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 ------------------------------------------------------- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.

3

Hi all,

re-issued GEOS-9191 pr[1] with new test cases to cover the issue that forced us to revert the other one.
I’ll leave it to you, Jody, to decide whether to include the 2.16.x backport on this release. IMHO it should be safe, and I tested manually with a data directory that has no gwc-layers directory with and without the fix commit and it seems all good.

Cheers,
Gabriel

[1] https://github.com/geoserver/geoserver/pull/3909
[2] https://github.com/geoserver/geoserver/pull/3909/commits/65cc9227b7a9138edb9313784d53e4c718158958

···

Gabriel Roldán

4

I will test myself locally and get back to you.

···

–
Jody Garnett

5

Gabriel my testing was fine, but I admit to being somewhat hesitant given fernando’s recent trouble.

I understand you wanting to clean up code. The strategy of removing null checks that should not happen is always risky (for when they happen).

···

–
Jody Garnett

6

Jody, let it slip till next release, don’t even waste your time.

(btw, the npe was a newly introduced issue of my own, the clean up of null checks is good and verified they were testing for nulls that couldn’t happen inside the internal code, not user input of any kind)

···

Gabriel Roldán

7

I am currently working on the geotools build, here are the details for the upcoming release.

GeoServer 2.16.1

···

Blog draft is ready for review, I have included stock headings for security updates / community updates / About 2.16 Series sections which I hope we can recycle each time.

Jody Garnett

8

Initial release artifacts are reading for testing:

https://build.geoserver.org/view/release/job/geoserver-release/261/artifact/distribution/2.16.1

I expect to release Friday (after folks have had a chance to try out the above and review the blog posts)

···

–
Jody Garnett

9

Once again ask folks to review blog post, and test the release artifacts above.
(I will be in a position to test mid-week)

···

–
Jody Garnett

10

Hi Jody

How can I get a WP login, so that I can help to review the blog post?

Regards

On Mon, 25 Nov 2019 at 06:32, Jody Garnett <jody.garnett@anonymised.com> wrote:

Once again ask folks to review blog post, and test the release artifacts above.
(I will be in a position to test mid-week)

–
Jody Garnett

On Thu, 21 Nov 2019 at 17:58, Jody Garnett <jody.garnett@anonymised.com> wrote:

Initial release artifacts are reading for testing:

https://build.geoserver.org/view/release/job/geoserver-release/261/artifact/distribution/2.16.1

I expect to release Friday (after folks have had a chance to try out the above and review the blog posts)

–
Jody Garnett

On Wed, 20 Nov 2019 at 21:37, Jody Garnett <jody.garnett@anonymised.com> wrote:

I am currently working on the geotools build, here are the details for the upcoming release.

GeoServer 2.16.1

Blog draft is ready for review, I have included stock headings for security updates / community updates / About 2.16 Series sections which I hope we can recycle each time.

Jody Garnett

On Wed, 20 Nov 2019 at 11:27, Gabriel Roldan <gabriel.roldan@anonymised.com3…> wrote:

Jody, let it slip till next release, don’t even waste your time.

(btw, the npe was a newly introduced issue of my own, the clean up of null checks is good and verified they were testing for nulls that couldn’t happen inside the internal code, not user input of any kind)

On Wed, 20 Nov 2019 at 14:59, Jody Garnett <jody.garnett@anonymised.com…> wrote:

Gabriel my testing was fine, but I admit to being somewhat hesitant given fernando’s recent trouble.

I understand you wanting to clean up code. The strategy of removing null checks that should not happen is always risky (for when they happen).

–
Jody Garnett

On Mon, 18 Nov 2019 at 10:34, Jody Garnett <jody.garnett@anonymised.com> wrote:

I will test myself locally and get back to you.

–
Jody Garnett

On Mon, 18 Nov 2019 at 06:20, Gabriel Roldan <gabriel.roldan@anonymised.com> wrote:

Hi all,

re-issued GEOS-9191 pr[1] with new test cases to cover the issue that forced us to revert the other one.
I’ll leave it to you, Jody, to decide whether to include the 2.16.x backport on this release. IMHO it should be safe, and I tested manually with a data directory that has no gwc-layers directory with and without the fix commit and it seems all good.

Cheers,
Gabriel

[1] https://github.com/geoserver/geoserver/pull/3909
[2] https://github.com/geoserver/geoserver/pull/3909/commits/65cc9227b7a9138edb9313784d53e4c718158958

On Mon, 18 Nov 2019 at 05:16, Andrea Aime <andrea.aime@anonymised.com.> wrote:

Reminder 2, 2.16.1 is a stable series release, so careful about what you backport

only a few days before the release

Cheers
Andrea

On Mon, Nov 18, 2019 at 6:38 AM Jody Garnett <jody.garnett@anonymised.com> wrote:

The GeoServer 2.16.2 release is scheduled for this week. If you have any fixes or pull requests this is your reminder :slight_smile:

–
Jody Garnett

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

–

Regards, Andrea Aime == 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 ------------------------------------------------------- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.

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

–

Gabriel Roldán

–

Gabriel Roldán

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

11

Hi guys

I’m not sure that my previous email was received by the list, so I’m asking again, hoping to find the WordPress administrator for the GeoServer blog - who would that be?

How can I get a WP login, so that I can help to review the blog post?

Regards

Peter

On Mon, 25 Nov 2019 at 10:56, Peter Smythe <gs@anonymised.com> wrote:

Hi Jody

How can I get a WP login, so that I can help to review the blog post?

Regards

On Mon, 25 Nov 2019 at 06:32, Jody Garnett <jody.garnett@anonymised.com> wrote:

Once again ask folks to review blog post, and test the release artifacts above.
(I will be in a position to test mid-week)

–
Jody Garnett

On Thu, 21 Nov 2019 at 17:58, Jody Garnett <jody.garnett@anonymised.com> wrote:

Initial release artifacts are reading for testing:

https://build.geoserver.org/view/release/job/geoserver-release/261/artifact/distribution/2.16.1

I expect to release Friday (after folks have had a chance to try out the above and review the blog posts)

–
Jody Garnett

On Wed, 20 Nov 2019 at 21:37, Jody Garnett <jody.garnett@…403…> wrote:

I am currently working on the geotools build, here are the details for the upcoming release.

GeoServer 2.16.1

Blog draft is ready for review, I have included stock headings for security updates / community updates / About 2.16 Series sections which I hope we can recycle each time.

Jody Garnett

On Wed, 20 Nov 2019 at 11:27, Gabriel Roldan <gabriel.roldan@anonymised.com3…> wrote:

Jody, let it slip till next release, don’t even waste your time.

(btw, the npe was a newly introduced issue of my own, the clean up of null checks is good and verified they were testing for nulls that couldn’t happen inside the internal code, not user input of any kind)

On Wed, 20 Nov 2019 at 14:59, Jody Garnett <jody.garnett@anonymised.com…> wrote:

Gabriel my testing was fine, but I admit to being somewhat hesitant given fernando’s recent trouble.

I understand you wanting to clean up code. The strategy of removing null checks that should not happen is always risky (for when they happen).

–
Jody Garnett

On Mon, 18 Nov 2019 at 10:34, Jody Garnett <jody.garnett@anonymised.com> wrote:

I will test myself locally and get back to you.

–
Jody Garnett

On Mon, 18 Nov 2019 at 06:20, Gabriel Roldan <gabriel.roldan@anonymised.com> wrote:

Hi all,

re-issued GEOS-9191 pr[1] with new test cases to cover the issue that forced us to revert the other one.
I’ll leave it to you, Jody, to decide whether to include the 2.16.x backport on this release. IMHO it should be safe, and I tested manually with a data directory that has no gwc-layers directory with and without the fix commit and it seems all good.

Cheers,
Gabriel

[1] https://github.com/geoserver/geoserver/pull/3909
[2] https://github.com/geoserver/geoserver/pull/3909/commits/65cc9227b7a9138edb9313784d53e4c718158958

On Mon, 18 Nov 2019 at 05:16, Andrea Aime <andrea.aime@anonymised.com.> wrote:

Reminder 2, 2.16.1 is a stable series release, so careful about what you backport

only a few days before the release

Cheers
Andrea

On Mon, Nov 18, 2019 at 6:38 AM Jody Garnett <jody.garnett@anonymised.com> wrote:

The GeoServer 2.16.2 release is scheduled for this week. If you have any fixes or pull requests this is your reminder :slight_smile:

–
Jody Garnett

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

–

Regards, Andrea Aime == 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 ------------------------------------------------------- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.

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

–

Gabriel Roldán

–

Gabriel Roldán

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

12

It looks like I can add you, thanks for offering to review.

···

–
Jody Garnett

13

Thanks for testing Jukka, and thanks to Peter for review blog post.

···

Jody Garnett

14

It seems I have messed up the build at the geotools level, I have reverted the blog post and will try again.

···

–
Jody Garnett

15

Release is out, email was sent to user list over the weekend.

(the prior message was me getting confused about version numbers and apparently needing more sleep)

···

–
Jody Garnett

16

Hi guys,
it looks like the download page http://geoserver.org/download/ has a 2.16.1 link but it still points to:
http://geoserver.org/release/2.16.0/ (2.16.0).

Cheers,
Daniele

···

Regards,
Daniele Romagnoli

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

Ing. Daniele Romagnoli
Senior Software Engineer

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

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

Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia.

This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.

17

Let me fix that …

···

–
Jody Garnett