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 <[email protected]
<mailto:[email protected]>> wrote:
On Sat, May 21, 2016 at 2:56 PM, Jody Garnett
<[email protected] <mailto:[email protected]>> 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
[email protected]
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
