On Fri, Mar 17, 2017 at 10:04 PM, Jody Garnett <[email protected]>
wrote:

> So the one I know of is the 
> *org.geotools.renderer.style.legacyAnchorPoint=true
> *flag introduced for the GeoTools 17-RC1.
>
> If we do want to preserve backwards compatibility we have some options:
> - configure this flag to true during startup
> - change the value based on strict=true (not sure how I feel about that)
>

I think we can leave it as is. As I said in reply to Jukka already, I'm not
saying we should never ever break backwards compatibility,
but that it should be a concern and part of the discussion when making
changes, get a feel of what's the benefit vs damage ratio,
and remember, if at all possible, to leave a mechanism to re-enable the
previous behavior

In my experience the majority of styles do not use the default label
> position, often having to manually offset it from original point
> symbolizer. I kind of wish we got some feedback from 2.11-RC1 release.
>

Eh... I think us developers have the wrong mental model about this, and/or
the general lack of presence on the user list put off the (small) part of
the user community that would be inclined to just test for the sake of
testing.

Someone doing production is not going to test RC, they are going to wait
for an actual need to upgrade, and then go straight for the current
stable/maintenance.
I see real trouble on the user base side upgrading at our current pace, and
I'm not talking about the 6 months cycle, but the 1 year one (when a series
just goes out of support).
The common upgrade I see is from a number of releases back, I work with
organisations that is still based on 2.4 and one that comes
to mind which is still running 2.2, with no intention to upgrade in the
short term.

Also, I find myself sometimes looking at all the announcements between
version x and y to answer the question of "what does an upgrade buy me?"
>From this point of view, and thinking about backwards compatibility issues,
I think it would be nice to have a single page with all
the main feature and backwards incompatible changes in each .0 release,
while it would not contain everything, it should
provide a useful quick summary for those making "long jump" upgrades.

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.

-------------------------------------------------------
------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Reply via email to