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.
--
Jody Garnett
On 21 May 2016 at 02:07, Andrea Aime <[email protected]> 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
>
> [1]: https://en.wikipedia.org/wiki/Freeze_(software_engineering)
>
> --
> ==
> 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
> [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
