> 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.
>
Oh I know, and understand it is a cultural change over time. As more people
get comfortable with "just using" open source we are losing some of that
we-are-all-in-this-together rebel feeling that helped make this more of a
collaboration with developers/users. On the plus side we are now the
establishment - and have to worry about implementing a standard wrong.
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.
>
This six-month release / 1 year support cycle is of course subject to
change. Right now I find the balance okay from a maintenance standpoint -
but backporting is a fixed cost (it does not matter how many releases we
make, it matters how far back in time we have to backport).
TLDR: I know the user community would love a three year LTS release - but
we have not sorted out a way to make that profitable/sustainable/fun.
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.
>
That is something we can work on for the docs, there is an update page in
the geotools docs that could also use an update.
>
> 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 <+39%200584%20962313>
> fax: +39 0584 1660272 <+39%200584%20166%200272>
> mob: +39 339 8844549 <+39%20339%20884%204549>
>
> 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
