[Geoserver-devel] Freeze for 2.9

Dear All,
I have talked to Andrea about whether or not we should unfreeze 2.9
given the delay for the upgrade to spring 4.

From the perspective of someone who follows clients deployments, I am

against unfreezing 2.9.
With the delay for 2.9 we are making room for a change which is major
(at least in the eyes of the users) and piling more changes on top
would defeat this delay, a simple as that.

I understand the push for releasing paid work, but I care more about stability.

Open to see what others think.

Regards,
Simone Giannecchini

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

Ing. Simone Giannecchini
@simogeo
Founder/Director

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

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.

I know I don’t get a vote since I am no longer PSC but as somone who contributes more than just bug fixes to the code base would this mean there would no longer be a branch open for new features until 2.9 branches off?

On Mon, Mar 14, 2016 at 5:54 AM Simone Giannecchini <simone.giannecchini@anonymised.com> wrote:

Dear All,
I have talked to Andrea about whether or not we should unfreeze 2.9
given the delay for the upgrade to spring 4.

From the perspective of someone who follows clients deployments, I am
against unfreezing 2.9.
With the delay for 2.9 we are making room for a change which is major
(at least in the eyes of the users) and piling more changes on top
would defeat this delay, a simple as that.

I understand the push for releasing paid work, but I care more about stability.

Open to see what others think.

Regards,
Simone Giannecchini

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

Ing. Simone Giannecchini
@simogeo
Founder/Director

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

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.


Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140


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

Ciao Justin,
for 2.9 we are already piling up the upgrade to wicket (which is
causing problems, see latest emails) with the upgrade to spring 2.4
which came in at the very last minute.
I guess we have allowed enough major changes wrt adding even more.

All the people I talk to demand more stability and maturity not more features.

We might want to decide to shring freeze time for 2.9 but I would not
want to add more changes.

Regards,
Simone Giannecchini

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

Ing. Simone Giannecchini
@simogeo
Founder/Director

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

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.

On Mon, Mar 14, 2016 at 3:31 PM, Justin Deoliveira <jdeolive@anonymised.com> wrote:

I know I don’t get a vote since I am no longer PSC but as somone who
contributes more than just bug fixes to the code base would this mean there
would no longer be a branch open for new features until 2.9 branches off?

On Mon, Mar 14, 2016 at 5:54 AM Simone Giannecchini
<simone.giannecchini@anonymised.com> wrote:

Dear All,
I have talked to Andrea about whether or not we should unfreeze 2.9
given the delay for the upgrade to spring 4.

>From the perspective of someone who follows clients deployments, I am
against unfreezing 2.9.
With the delay for 2.9 we are making room for a change which is major
(at least in the eyes of the users) and piling more changes on top
would defeat this delay, a simple as that.

I understand the push for releasing paid work, but I care more about
stability.

Open to see what others think.

Regards,
Simone Giannecchini

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

Ing. Simone Giannecchini
@simogeo
Founder/Director

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

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.

------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Looks like it is a non-issue, the vast majority of the spring4 migration is done (thanks Justin, Kevin and Christian) and we now have testing to do.

If I get the word from Justin I will make a beta2 this week, and we can get back on the release train … looking something like:

  • 17 March 2.9-beta2
  • 31 March 2.9-RC1

To answer your question Justin, we would make a new master branch for the RC1.

···

On 14 March 2016 at 05:51, Simone Giannecchini <simone.giannecchini@anonymised.com> wrote:

Dear All,
I have talked to Andrea about whether or not we should unfreeze 2.9
given the delay for the upgrade to spring 4.

From the perspective of someone who follows clients deployments, I am
against unfreezing 2.9.
With the delay for 2.9 we are making room for a change which is major
(at least in the eyes of the users) and piling more changes on top
would defeat this delay, a simple as that.

I understand the push for releasing paid work, but I care more about stability.

Open to see what others think.

Regards,
Simone Giannecchini

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

Ing. Simone Giannecchini
@simogeo
Founder/Director

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

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.


Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140


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


Jody Garnett

On Mon, Mar 14, 2016 at 4:22 PM, Jody Garnett <jody.garnett@anonymised.com>
wrote:

Looks like it is a non-issue, the vast majority of the spring4 migration
is done (thanks Justin, Kevin and Christian) and we now have testing to do.

If I get the word from Justin I will make a beta2 this week, and we can
get back on the release train ... looking something like:

- 17 March 2.9-beta2
- 31 March 2.9-RC1

We just upgraded the entire underpinnings of GeoServer and you want to give
it two weeks only
for testing before going out with a RC...
I guess you forgot about the agreement to delay the release _two_ months
(the original discussion
was about 3 actually), not one.
The reasoning was simple, the issue is not upgrading the code so that it
builds (which I agreed could have been
done within a month) but testing it manually, which hasn't happened yet as
far as I know, or at
least, I missed the message, all the mails I've seen talk about "just
started GeoServer, it appears to work".

That said, I see the tension between new development and stability, but I
guess since we
are already working outside of the normal rules, we could do the following,
that has the agreed
two months delay along with open field for development:

- March 18th: 2.9-beta2 and branch off 2.9.x
- April 18th: 2.9-RC
- May 18th: 2.9 final

Of course the above works if people are actually going to hand test the
2.9.x release,
if not and everybody just merrily starts working on 2.10.x, we are indeed
just wasting time

Cheers
Andrea

--

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.

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

Sounds good. And to be clear I wasn’t advocating for a freeze or non-freeze, just asking the question so that I don’t commit something by mistake.

···


Jody Garnett

On 14 March 2016 at 05:51, Simone Giannecchini <simone.giannecchini@anonymised.com> wrote:

Dear All,
I have talked to Andrea about whether or not we should unfreeze 2.9
given the delay for the upgrade to spring 4.

From the perspective of someone who follows clients deployments, I am
against unfreezing 2.9.
With the delay for 2.9 we are making room for a change which is major
(at least in the eyes of the users) and piling more changes on top
would defeat this delay, a simple as that.

I understand the push for releasing paid work, but I care more about stability.

Open to see what others think.

Regards,
Simone Giannecchini

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

Ing. Simone Giannecchini
@simogeo
Founder/Director

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

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.


Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140


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

Forgive my enthusiasm - I am rather stoked that the initial “getting it to work” has only taken a week, rather than several weeks. I had thought we would be wrestling much longer with secruity and security-cas …

Updating the wiki now with test plan (emphasis rest-api, security, security ldap, security cas). Looks like I need to dig into the communityRelease modules, and geofence.

But yeah I will turn this around and only update the schedule when the testing is complete. We can ask the user-list for help with a nightly build once we are “code complete”.

···

On 14 March 2016 at 09:40, Andrea Aime <andrea.aime@anonymised.com> wrote:


Jody Garnett

On Mon, Mar 14, 2016 at 4:22 PM, Jody Garnett <jody.garnett@anonymised.com> wrote:

Looks like it is a non-issue, the vast majority of the spring4 migration is done (thanks Justin, Kevin and Christian) and we now have testing to do.

If I get the word from Justin I will make a beta2 this week, and we can get back on the release train … looking something like:

  • 17 March 2.9-beta2
  • 31 March 2.9-RC1

We just upgraded the entire underpinnings of GeoServer and you want to give it two weeks only
for testing before going out with a RC…
I guess you forgot about the agreement to delay the release two months (the original discussion
was about 3 actually), not one.
The reasoning was simple, the issue is not upgrading the code so that it builds (which I agreed could have been
done within a month) but testing it manually, which hasn’t happened yet as far as I know, or at
least, I missed the message, all the mails I’ve seen talk about “just started GeoServer, it appears to work”.

That said, I see the tension between new development and stability, but I guess since we

are already working outside of the normal rules, we could do the following, that has the agreed
two months delay along with open field for development:

  • March 18th: 2.9-beta2 and branch off 2.9.x
  • April 18th: 2.9-RC
  • May 18th: 2.9 final

Of course the above works if people are actually going to hand test the 2.9.x release,
if not and everybody just merrily starts working on 2.10.x, we are indeed just wasting time

Cheers
Andrea

==
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.


Hi Jody,
so what’s the revised plan?

Cheers
Andrea

···

On Mon, Mar 14, 2016 at 5:00 PM, Jody Garnett <jody.garnett@anonymised.com> wrote:

Forgive my enthusiasm - I am rather stoked that the initial “getting it to work” has only taken a week, rather than several weeks. I had thought we would be wrestling much longer with secruity and security-cas …

Updating the wiki now with test plan (emphasis rest-api, security, security ldap, security cas). Looks like I need to dig into the communityRelease modules, and geofence.

But yeah I will turn this around and only update the schedule when the testing is complete. We can ask the user-list for help with a nightly build once we are “code complete”.


Jody Garnett

On 14 March 2016 at 09:40, Andrea Aime <andrea.aime@anonymised.com> wrote:

On Mon, Mar 14, 2016 at 4:22 PM, Jody Garnett <jody.garnett@anonymised.com…403…> wrote:

Looks like it is a non-issue, the vast majority of the spring4 migration is done (thanks Justin, Kevin and Christian) and we now have testing to do.

If I get the word from Justin I will make a beta2 this week, and we can get back on the release train … looking something like:

  • 17 March 2.9-beta2
  • 31 March 2.9-RC1

We just upgraded the entire underpinnings of GeoServer and you want to give it two weeks only
for testing before going out with a RC…
I guess you forgot about the agreement to delay the release two months (the original discussion
was about 3 actually), not one.
The reasoning was simple, the issue is not upgrading the code so that it builds (which I agreed could have been
done within a month) but testing it manually, which hasn’t happened yet as far as I know, or at
least, I missed the message, all the mails I’ve seen talk about “just started GeoServer, it appears to work”.

That said, I see the tension between new development and stability, but I guess since we

are already working outside of the normal rules, we could do the following, that has the agreed
two months delay along with open field for development:

  • March 18th: 2.9-beta2 and branch off 2.9.x
  • April 18th: 2.9-RC
  • May 18th: 2.9 final

Of course the above works if people are actually going to hand test the 2.9.x release,
if not and everybody just merrily starts working on 2.10.x, we are indeed just wasting time

Cheers
Andrea

==
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.


==
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.


Thanks to everyone for contributing to the email discussion (not sure if I have the wiki up to date).

I have two questions:

Q: Kevin how close is geowebcache to being ready? You were looking at upgrading security component …

Q: Does any work need to be done “upstream” in the GeoFence project before the GeoServer community modules can be fixed?

···

After beta2 (and testing) I get the impression GeoSolutions would like to have more time to battle harden the result. I do not mind how much time, only that we decide together.

a) if it is 1-2 months (which is totally reasonable) I would like to end the code freeze - and we can make a beta2 “when ready”.
b) if it is 1-2 weeks (which is also reasonable given how fast the upgrade was performed) I would like maintain the code free - I understand that this as a cost to all involved.


Jody Garnett

update:

···

Q: Kevin how close is geowebcache to being ready? You were looking at upgrading security component …

Talked to Kevin, update to spring security is slow going - but still going.

I managed to make a big jump in the Acegi to Spring Security update shortly after talking to Jody. It now seems to be working.

There were a bunch of things in the old setup that seemed to be just boilerplate that SpringSecurity now does automatically, and some things that seemed not to be used at all such as HTTP method based rules for the REST API that appeared to be intended to allow non-admins to do GETs against the REST admin API which is obviously a bad idea, and thankfully wasn’t working. I may have misunderstood what it was doing though so I may have broken some obscure feature I wasn’t familiar with.

Kevin Michael Smith

smithkm@anonymised.com

On Wed, Mar 16, 2016, at 04:03 PM, Jody Garnett wrote:

update:

Q: Kevin how close is geowebcache to being ready? You were looking at upgrading security component …

Talked to Kevin, update to spring security is slow going - but still going.


Transform Data into Opportunity.

Accelerate data analysis in your applications with

Intel Data Analytics Acceleration Library.

Click to learn more.

http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140


Geoserver-devel mailing list

Geoserver-devel@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Looking at geofence:

3.1.1.RELEASE

3.1.0.RELEASE

There are lots of other dependencies to sync up (servlet, jettison, asm, …).

···

On 16 March 2016 at 14:54, Jody Garnett <jody.garnett@anonymised.com> wrote:

Thanks to everyone for contributing to the email discussion (not sure if I have the wiki up to date).

I have two questions:

Q: Kevin how close is geowebcache to being ready? You were looking at upgrading security component …

Q: Does any work need to be done “upstream” in the GeoFence project before the GeoServer community modules can be fixed?


Jody Garnett

After beta2 (and testing) I get the impression GeoSolutions would like to have more time to battle harden the result. I do not mind how much time, only that we decide together.

a) if it is 1-2 months (which is totally reasonable) I would like to end the code freeze - and we can make a beta2 “when ready”.
b) if it is 1-2 weeks (which is also reasonable given how fast the upgrade was performed) I would like maintain the code free - I understand that this as a cost to all involved.


Jody Garnett