[Geoserver-devel] PR fix round up

GeoServer GeoServer Developer
1

Thanks for fixing both a security issue and chache issue Andrea. I think we also have fixes from Devon and Kevin for tomorrow’s release.

Any others scheduled?

–
Jody Garnett

2

Please update the release schedule:
https://github.com/geoserver/geoserver/wiki/Release-Schedule

On 18/04/17 00:33, Jody Garnett wrote:

Thanks for fixing both a security issue and chache issue Andrea. I think we
also have fixes from Devon and Kevin for tomorrow's release.

Any others scheduled?

------------------------------------------------------------------------------
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@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/&gt;
New Zealand

3

Done

Ian

···

On 17 April 2017 at 23:59, Ben Caradoc-Davies <ben@anonymised.com> wrote:

Please update the release schedule:
https://github.com/geoserver/geoserver/wiki/Release-Schedule

On 18/04/17 00:33, Jody Garnett wrote:

Thanks for fixing both a security issue and chache issue Andrea. I think we
also have fixes from Devon and Kevin for tomorrow’s release.

Any others scheduled?

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.comsourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

–
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <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

–

Ian Turton

4

Thanks!

On 18/04/17 19:39, Ian Turton wrote:

Done

Ian

On 17 April 2017 at 23:59, Ben Caradoc-Davies <ben@anonymised.com> wrote:

Please update the release schedule:
https://github.com/geoserver/geoserver/wiki/Release-Schedule

On 18/04/17 00:33, Jody Garnett wrote:

Thanks for fixing both a security issue and chache issue Andrea. I think

we

also have fixes from Devon and Kevin for tomorrow's release.

Any others scheduled?

------------------------------------------------------------

------------------

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@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/&gt;
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@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/&gt;
New Zealand

5

Would it be a good idea to backport GSIP 152 - Layer group security for this release? I see a backport to 2.10 discussed in the proposal, but it doesn’t seem to have been backported yet.

Torben

···

On Tue, Apr 18, 2017 at 5:44 AM, Ben Caradoc-Davies <ben@anonymised.com> wrote:

Thanks!

On 18/04/17 19:39, Ian Turton wrote:

Done

Ian

On 17 April 2017 at 23:59, Ben Caradoc-Davies <ben@anonymised.com> wrote:

Please update the release schedule:
https://github.com/geoserver/geoserver/wiki/Release-Schedule

On 18/04/17 00:33, Jody Garnett wrote:

Thanks for fixing both a security issue and chache issue Andrea. I think
we
also have fixes from Devon and Kevin for tomorrow’s release.

Any others scheduled?

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.comsourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

–
Ben Caradoc-Davies <ben@anonymised.com91…>
Director
Transient Software Limited <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.comsourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

–
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <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

6

Hi Torben,
I wanted to, but Jody expressed a negative opinion (or one that sounded like negative).
At this point it’s too late, too close to the release to merge something that big,
but it could be merged for the next if there is interest?

Mind, you’ll also have to merge the opaque groups one, they go in pair (the security
work was made more efficient and received fixes during with the opaque groups work).

Cheers
Andrea

···

On Tue, Apr 18, 2017 at 6:26 PM, Torben Barsballe <tbarsballe@anonymised.com> wrote:

Would it be a good idea to backport GSIP 152 - Layer group security for this release? I see a backport to 2.10 discussed in the proposal, but it doesn’t seem to have been backported yet.

Torben

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

–

On Tue, Apr 18, 2017 at 5:44 AM, Ben Caradoc-Davies <ben@anonymised.com> wrote:

Thanks!

On 18/04/17 19:39, Ian Turton wrote:

Done

Ian

On 17 April 2017 at 23:59, Ben Caradoc-Davies <ben@anonymised.com> wrote:

Please update the release schedule:
https://github.com/geoserver/geoserver/wiki/Release-Schedule

On 18/04/17 00:33, Jody Garnett wrote:

Thanks for fixing both a security issue and chache issue Andrea. I think
we
also have fixes from Devon and Kevin for tomorrow’s release.

Any others scheduled?

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

–
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <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

–
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <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.