[Geoserver-devel] Feature freeze: do we need to amend our release process?

GeoServer GeoServer Developer
1

Hi,
looking at the recent changes on the 2.9.x branch I see two new features/improvements
landing right before the final release:
https://github.com/geoserver/geoserver/commit/179023a13fe2337407fbcb9137d106cf2c283372

https://github.com/geoserver/geoserver/commit/6d5299349382b9f6fe85a46d432f4e988aa34833
This last one is so small that I would not have complained about it by itself, but the first one is

definitely larger, even if well tested.

Our release guide states that we should be in “feature freeze” right now:
http://docs.geoserver.org/stable/en/developer/policies/community-process.html#release-cycle

I can only guess that people merging those pull requests on 2.9.x are giving a different meaning to “feature freeze” 1, compared
to our practice of to only merging bug fixes, and be very careful with those too right before cutting a release (as practice shows,
a bug fix can unintendedly introduce other bugs).

I’m not against change per se, practices do evolve over time, but I believe it should be discussed in order to give everybody the same rules and opportunities,
otherwise we end up with an opaque process and lose openness, which would be even worse than losing stability and/or quality.

Can we discuss a bit about whether:

  • It’s acceptable for the release quality to add last minute changes that are not bug fixes, and if so, do we want to drop the feature freeze?
  • What kind of changes are meant to be blocked during the feature freeze, and if the notion is a bit relaxed (and thus could spur debate),
    what process needs to be followed in order to port back these improvements to the freeze. Like, feature backport to stable in normal conditions would require a quick mailing list vote, what would be the process to add a feature/improvement during feature freeze?

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.

2

+1 for retaining the freeze.

New features in the hours before a release should be the exception, discussed in public, and subjected to extra scrutiny. In the case of the JSON commit, I saw no discussion, just a Jira issue made at the same time as the commit. Did I miss something? This commit hit 2.9.x at the same moment it hit master. The commit itself looks great, and thanks to the submitter and committer for their efforts, but could this have waited until after the freeze? Could it have spent some time on master before backport? Given the problems getting to 2.9.0, I am reluctant to take unnecessary chances.

Kind regards,
Ben.

On 21/05/16 21:07, Andrea Aime wrote:

    - It's acceptable for the release quality to add last minute changes
    that are not bug fixes, and if so, do we want to drop the feature freeze?

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

3

The first feature was discussed at the skype meeting, it has been waiting on docs for quite some time and is important to the downstream GeoMesa project. I figured if James was willing to attend our meeting to coordinate and explain its importance that I could help with the docs and see that it was included.

I had not expected the second feature to be backported, although I agree it is small.

···

On 21 May 2016 at 02:07, Andrea Aime <andrea.aime@anonymised.com> wrote:

Hi,
looking at the recent changes on the 2.9.x branch I see two new features/improvements
landing right before the final release:
https://github.com/geoserver/geoserver/commit/179023a13fe2337407fbcb9137d106cf2c283372

https://github.com/geoserver/geoserver/commit/6d5299349382b9f6fe85a46d432f4e988aa34833
This last one is so small that I would not have complained about it by itself, but the first one is

definitely larger, even if well tested.

Our release guide states that we should be in “feature freeze” right now:
http://docs.geoserver.org/stable/en/developer/policies/community-process.html#release-cycle

I can only guess that people merging those pull requests on 2.9.x are giving a different meaning to “feature freeze” 1, compared
to our practice of to only merging bug fixes, and be very careful with those too right before cutting a release (as practice shows,
a bug fix can unintendedly introduce other bugs).

I’m not against change per se, practices do evolve over time, but I believe it should be discussed in order to give everybody the same rules and opportunities,
otherwise we end up with an opaque process and lose openness, which would be even worse than losing stability and/or quality.

Can we discuss a bit about whether:

  • It’s acceptable for the release quality to add last minute changes that are not bug fixes, and if so, do we want to drop the feature freeze?
  • What kind of changes are meant to be blocked during the feature freeze, and if the notion is a bit relaxed (and thus could spur debate),
    what process needs to be followed in order to port back these improvements to the freeze. Like, feature backport to stable in normal conditions would require a quick mailing list vote, what would be the process to add a feature/improvement during feature freeze?

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.

Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j

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

–
Jody Garnett

4

On Sat, May 21, 2016 at 2:56 PM, Jody Garnett <jody.garnett@anonymised.com>
wrote:

The first feature was discussed at the skype meeting, it has been waiting
on docs for quite some time and is important to the downstream GeoMesa
project. I figured if James was willing to attend our meeting to coordinate
and explain its importance that I could help with the docs and see that it
was included.

Did you have PSC majority during the meeting, was there a vote? What
project procedure did you call upon
to justify the backport during feature freeze?
Has the voice meeting become the place where "real decisions" are made,
regardless of the PSC?
That would also require an amendment to procedures I guess.

Ben was apparently at the meeting, and yet he looks surprised by the
backport, was it actually discussed to start with?

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.

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

5

I acted as the volunteer making the release.

I am happy to back out the change if the mailing list considers it appropriate. This release has many problems, including a long delay, and I do not want to get held up over an improvement to JSON formatting.

···

On 21 May 2016 at 06:02, Andrea Aime <andrea.aime@anonymised.com> wrote:

–
Jody Garnett

On Sat, May 21, 2016 at 2:56 PM, Jody Garnett <jody.garnett@anonymised.com> wrote:

The first feature was discussed at the skype meeting, it has been waiting on docs for quite some time and is important to the downstream GeoMesa project. I figured if James was willing to attend our meeting to coordinate and explain its importance that I could help with the docs and see that it was included.

Did you have PSC majority during the meeting, was there a vote? What project procedure did you call upon
to justify the backport during feature freeze?
Has the voice meeting become the place where “real decisions” are made, regardless of the PSC?
That would also require an amendment to procedures I guess.

Ben was apparently at the meeting, and yet he looks surprised by the backport, was it actually discussed to start with?

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.

6

Hi all,

Sorry for the confusion I may have caused. My attendance was to help track a particular GeoTools PR to handle unavailable factories. The issue came up while testing GeoMesa with GeoTools 15-RC1. Jody’s PR here (1) was to help fix that. Simone and Andrea had left some helpful feedback, and I wanted to know if I could do anything to help wrap up that work. That PR is mentioned briefly in the meeting round-up.

On Tuesday, as we continued through the PRs, Jody asked about Andrew’s JSON work (2). He thought it had been ready to merge for a few weeks pending a fix to the compilation issues. Since Jody seemed to be ok with merging the PR, I addressed the build error.

That discussion wasn’t captured in the meeting notes, and there was no vote to include the PR. Tuesday’s meeting was a tough one for communication.

I see no problem in reverting the commit on the 2.9.x series.

Cheers,

Jim

  1. https://github.com/geotools/geotools/pull/1192
    (This blocker did get merged here: https://github.com/geotools/geotools/commit/3a8373cdd95689ec979a62606afcf6f533f32d8b?diff=unified. Thanks!)

  2. https://github.com/geoserver/geoserver/pull/1524

···

On 5/21/2016 9:06 AM, Jody Garnett wrote:

I acted as the volunteer making the release.

I am happy to back out the change if the mailing list considers it appropriate. This release has many problems, including a long delay, and I do not want to get held up over an improvement to JSON formatting.

–
Jody Garnett

On 21 May 2016 at 06:02, Andrea Aime <andrea.aime@anonymised.com> wrote:

On Sat, May 21, 2016 at 2:56 PM, Jody Garnett <jody.garnett@anonymised.com> wrote:

The first feature was discussed at the skype meeting, it has been waiting on docs for quite some time and is important to the downstream GeoMesa project. I figured if James was willing to attend our meeting to coordinate and explain its importance that I could help with the docs and see that it was included.

Did you have PSC majority during the meeting, was there a vote? What project procedure did you call upon
to justify the backport during feature freeze?
Has the voice meeting become the place where “real decisions” are made, regardless of the PSC?
That would also require an amendment to procedures I guess.

Ben was apparently at the meeting, and yet he looks surprised by the backport, was it actually discussed to start with?

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.

------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
[https://ad.doubleclick.net/ddm/clk/304595813;131938128;j](https://ad.doubleclick.net/ddm/clk/304595813;131938128;j)

_______________________________________________
Geoserver-devel mailing list
[Geoserver-devel@lists.sourceforge.net](mailto:Geoserver-devel@lists.sourceforge.net)
[https://lists.sourceforge.net/lists/listinfo/geoserver-devel](https://lists.sourceforge.net/lists/listinfo/geoserver-devel)
7

On Sat, May 21, 2016 at 4:12 PM, Jim Hughes <jnh5y@anonymised.com> wrote:

Hi all,

Sorry for the confusion I may have caused. My attendance was to help
track a particular GeoTools PR to handle unavailable factories. The issue
came up while testing GeoMesa with GeoTools 15-RC1. Jody's PR here (1) was
to help fix that. Simone and Andrea had left some helpful feedback, and I
wanted to know if I could do anything to help wrap up that work. That PR
is mentioned briefly in the meeting round-up.

Yep, that is a bug fix, there is no confusion over that, it can and should
get in.

On Tuesday, as we continued through the PRs, Jody asked about Andrew's
JSON work (2). He thought it had been ready to merge for a few weeks
pending a fix to the compilation issues. Since Jody seemed to be ok with
merging the PR, I addressed the build error.

That discussion wasn't captured in the meeting notes, and there was no
vote to include the PR. Tuesday's meeting was a tough one for
communication.

I see no problem in reverting the commit on the 2.9.x series.

Personally I am not feeling a big pressure about getting it out, it's not
the commit per se that I'm concerned about,
more the notion that a release manager feel its ok to act on his own, in
clear violation of the existing procedures,
without feeling a need to discuss his actions with the PSC.

The original pull request in question was opened March 2, one day late for
2.9-beta1. It was not merged by beta2, April
22nd, it was not merged in time for RC1, May 5th, and all of a sudden it
gets merged right before 2.9.0 final, with
no discussion with the PSC, even if we are way deep in feature freeze. I
hope you understand my surprise.
Hence my initial discussion about whether or not we should have a procedure
change.

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.

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

8

On Sat, May 21, 2016 at 12:39 PM, Ben Caradoc-Davies <ben@anonymised.com>
wrote:

+1 for retaining the freeze.

New features in the hours before a release should be the exception,
discussed in public, and subjected to extra scrutiny.

Fully agreed, this is the way it should be. The current procedure actually
demands such behavior during the entire feature freeze.

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.

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

9

On 22/05/16 01:02, Andrea Aime wrote:

Ben was apparently at the meeting, and yet he looks surprised by the
backport, was it actually discussed to start with?

Andrea, I remember the discussion of the JSON work. I did not appreciate that there was an intention to backport. This was not minuted.

Kind regards,

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

10

Jim,

I see no benefit in reverting this commit. Your and Andrew's contribution is appreciated. The backport was not your action. Jody was a blur of constructive and helpful activity, but no good deed goes unpunished.

Andrea, thank you for bringing this to our attention. I think this is a learning experience: the freeze must be observed, and exceptions must be discussed on the mailing list so that decision-making is transparent and inclusive. Are you happy for the JSON commit to remain on 2.9.x, or would you prefer that it be reverted? I think we accept that its inclusion was a deviation from procedure.

Kind regards,
Ben.

On 22/05/16 02:12, Jim Hughes wrote:

Hi all,

Sorry for the confusion I may have caused. My attendance was to help
track a particular GeoTools PR to handle unavailable factories. The
issue came up while testing GeoMesa with GeoTools 15-RC1. Jody's PR
here (1) was to help fix that. Simone and Andrea had left some helpful
feedback, and I wanted to know if I could do anything to help wrap up
that work. That PR is mentioned briefly in the meeting round-up.

On Tuesday, as we continued through the PRs, Jody asked about Andrew's
JSON work (2). He thought it had been ready to merge for a few weeks
pending a fix to the compilation issues. Since Jody seemed to be ok
with merging the PR, I addressed the build error.

That discussion wasn't captured in the meeting notes, and there was no
vote to include the PR. Tuesday's meeting was a tough one for
communication.

I see no problem in reverting the commit on the 2.9.x series.

Cheers,

Jim

1. https://github.com/geotools/geotools/pull/1192
(This blocker did get merged here:
https://github.com/geotools/geotools/commit/3a8373cdd95689ec979a62606afcf6f533f32d8b?diff=unified.
Thanks!)

2. https://github.com/geoserver/geoserver/pull/1524

On 5/21/2016 9:06 AM, Jody Garnett wrote:

I acted as the volunteer making the release.

I am happy to back out the change if the mailing list considers it
appropriate. This release has many problems, including a long delay,
and I do not want to get held up over an improvement to JSON formatting.

--
Jody Garnett

On 21 May 2016 at 06:02, Andrea Aime <andrea.aime@anonymised.com
<mailto:andrea.aime@anonymised.com>> wrote:

    On Sat, May 21, 2016 at 2:56 PM, Jody Garnett
    <jody.garnett@anonymised.com <mailto:jody.garnett@anonymised.com>> wrote:

        The first feature was discussed at the skype meeting, it has
        been waiting on docs for quite some time and is important to
        the downstream GeoMesa project. I figured if James was willing
        to attend our meeting to coordinate and explain its importance
        that I could help with the docs and see that it was included.

    Did you have PSC majority during the meeting, was there a vote?
    What project procedure did you call upon
    to justify the backport during feature freeze?
    Has the voice meeting become the place where "real decisions" are
    made, regardless of the PSC?
    That would also require an amendment to procedures I guess.

    Ben was apparently at the meeting, and yet he looks surprised by
    the backport, was it actually discussed to start with?

    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 <tel:%2B39%200584%20962313>
    fax: +39 0584 1660272 <tel:%2B39%200584%201660272>
    mob: +39 339 8844549 <tel:%2B39%20%C2%A0339%208844549>

    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.

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

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

Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data
untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j

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

------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j

_______________________________________________
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

11

And this is the slippery slope: when one person backports features during the freeze, soon everyone will do it.

On 22/05/16 00:56, Jody Garnett wrote:

I had not expected the second feature to be backported, although I agree it
is small.

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

12

Ben,
Very well said. A hard rule is harsh for sure, but easy to apply and fair at the same time. Once we let go even a small bit, the erosion is inevitable and sooner than one we expect we’ll find ourselves dealing with large or dangerous backports

Cheers
Andrea

Il 21/mag/2016 23:04, “Ben Caradoc-Davies” <ben@anonymised.com> ha scritto:

And this is the slippery slope: when one person backports features during the freeze, soon everyone will do it.

On 22/05/16 00:56, Jody Garnett wrote:

I had not expected the second feature to be backported, although I agree it
is small.

–

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

13

On Sat, May 21, 2016 at 11:02 PM, Ben Caradoc-Davies <ben@anonymised.com>
wrote:

Andrea, thank you for bringing this to our attention. I think this is a
learning experience: the freeze must be observed, and exceptions must be
discussed on the mailing list so that decision-making is transparent and
inclusive. Are you happy for the JSON commit to remain on 2.9.x, or would
you prefer that it be reverted? I think we accept that its inclusion was a
deviation from procedure.

Ben, I have no issues with the commit staying on 2.9.x, I just don't want
to see this happening again without a proper open discussion.

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.

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

14

On 22/05/16 20:18, Andrea Aime wrote:

Ben, I have no issues with the commit staying on 2.9.x, I just don't want
to see this happening again without a proper open discussion.

Agreed.

Kind regards,

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

15

On Sun, May 22, 2016 at 10:18 AM, Andrea Aime
<andrea.aime@anonymised.com> wrote:

On Sat, May 21, 2016 at 11:02 PM, Ben Caradoc-Davies <ben@anonymised.com>
wrote:

Andrea, thank you for bringing this to our attention. I think this is a
learning experience: the freeze must be observed, and exceptions must be
discussed on the mailing list so that decision-making is transparent and
inclusive. Are you happy for the JSON commit to remain on 2.9.x, or would
you prefer that it be reverted? I think we accept that its inclusion was a
deviation from procedure.

Ben, I have no issues with the commit staying on 2.9.x, I just don't want to
see this happening again without a proper open discussion.

Same here.

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.

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

------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel