Hi Jody,
I'm strongly against this approach, people may test it if they see
something new they are interested into,
we cannot give them priorities, they are not there to help us, never have
been so far at least,
best we can hope is that they have their own self interest is matching ours.

Please, let's go back to the usual approach, full announcement with
pictures. The focus on just trying
an upgrade is also a good one, can we put it in a prominent place? Like
both top and bottom of the message?

Cheers
Andrea


On Sat, Mar 14, 2020 at 7:38 AM Jody Garnett <[email protected]> wrote:

> I have created a draft announcement, using a different approach than
> normal. Since this is a release candidate I have strictly focused on a call
> for testing, promising a details on new features when the 2.17.0 release is
> made.
>
> Here is a snippet:
>
> *This is a GeoServer release candidate made in conjunction with GeoTools
> 23-RC and GeoWebCache 1.17-RC.*
>
>
>    - *Release candidates are a community building exercise and are not
>       intended for production use.*
>       - *We ask the community (everyone: individuals, service providers,
>       organizations) to download and thoroughly test this release and report
>       back.*
>       - *Participating in testing release candidates is a key expectation
>       of our open source social contract
>       <http://www.ianturton.com/talks/foss4g.html#/>. We make an effort to 
> thank
>       each person who tests in our release announcement and project
>       presentations!*
>
> *We will provide a more extensive description of new functionality when
> GeoServer 2.17 is released.*
>
> I would like review (please) and ideas for testing priorities:
> 1. Test with your own data
> 2. Test download bundles work (I know my own tests are in a prior email)
> 3. Test MBStyle since it has had so much work done
> 4, Security tab for workspaces, layers and layergroups
>
> Any other priorities for testing? Checking recent proposals
> <https://github.com/geoserver/geoserver/wiki/Proposals> has a lot of
> content.
>
> --
> Jody Garnett
>
>
> On Fri, 13 Mar 2020 at 17:25, Jody Garnett <[email protected]> wrote:
>
>> Testing, with a bit more caution than usual
>>
>> *geoserver-2.17-RC-bin.zip*
>> - VERSION.txt - looks correct
>> - RUNNING.txt - correctly updated with openjdk and adoptopenjdk
>> - README.txt - generic but correct
>> - NOTICE.md - has the summary of all the license stuff
>> - GPL.md - GPL license (I do not see any of the other licenses)
>> - modules/ - JETTY specific configuration, I suspect RUNNING.txt could
>> mention this
>> - resources/log4j.properties - not sure if this is needed
>> bin/start.sh - worked fine
>> - application runs fine, no issues with desk testing
>> - server status / modules - not a lot of information here
>> - sever status / system status - working fine, amused to see fan speeds
>> - tools - page loads at all
>> bin/shutdown.sh - worked fine
>>
>> *geoserver-2.17-RC-htmldoc.zip*
>> - unpacks into geoserver-2.17-RC-htmldoc folder now (hopefully fine)
>> - readme - describes api, user, developer (perhaps this should be html
>> file)
>> - api - is missing
>> - user - content is fine, has "GeoServer 2.17-RC User Manual" in header
>> and page title
>> - developer - content is fine
>> - CC Attribution license missing
>> - confirmed in logs: build_release.sh zipped the logs, did not find the
>> assembly
>>
>> *geoserver-2.17-RC-javadoc*
>> - NOTICE.md, GPL.md included
>> - contents are fine
>>
>> *geoserver-2.17-RC-war*
>> NOTICE.md, GPL.md, VERSION.txt included
>> - not all licenses as expected
>> geoserver/WEB-INF/lib
>> - no SNAPSHOT jars included
>> - "listenablefuture-9999.0-empty-to-avoid-conflict-with-guava.jar" <--
>> not sure I know this story
>>
>> *extensions*
>> geoserver-2.17-RC-app-schema-plugin.zip
>> geoserver-2.17-RC-authkey-plugin.zip - *no license* or readme
>> geoserver-2.17-RC-cas-plugin.zip - *no license*
>> geoserver-2.17-RC-charts-plugin.zip
>> geoserver-2.17-RC-control-flow-plugin.zip *- not packaged as a folder
>> just a single jar*
>> geoserver-2.17-RC-css-plugin.zip - no readme
>> geoserver-2.17-RC-csw-plugin.zip - no readme
>> geoserver-2.17-RC-db2-plugin.zip - readme out of date (mentions "gt2-db2")
>> geoserver-2.17-RC-dxf-plugin.zip
>> geoserver-2.17-RC-excel-plugin.zip
>> geoserver-2.17-RC-feature-pregeneralized-plugin.zip - no readme
>> geoserver-2.17-RC-gdal-plugin.zip - could stand to have the image license
>> details here
>> geoserver-2.17-RC-geofence-plugin.zip - no readme
>> geoserver-2.17-RC-geofence-server-plugin.zip - no readme
>> geoserver-2.17-RC-grib-plugin.zip - no readme
>> geoserver-2.17-RC-h2-plugin.zip - no readme
>> geoserver-2.17-RC-imagemap-plugin.zip - no readme
>> geoserver-2.17-RC-imagemosaic-jdbc-plugin.zip - no readme
>> geoserver-2.17-RC-importer-bdb-plugin.zip - no readme
>> geoserver-2.17-RC-importer-plugin.zip - no readme
>> geoserver-2.17-RC-inspire-plugin.zip - no readme
>> geoserver-2.17-RC-jp2k-plugin.zip - could use imageio license
>> geoserver-2.17-RC-libjpeg-turbo-plugin.zip - could use imageio license,
>> no readme
>> geoserver-2.17-RC-mbstyle-plugin.zip
>> geoserver-2.17-RC-mongodb-plugin.zip - no readme
>> geoserver-2.17-RC-monitor-plugin.zip - readme
>> geoserver-2.17-RC-mysql-plugin.zip - no readme
>> geoserver-2.17-RC-netcdf-out-plugin.zip - no readme
>> geoserver-2.17-RC-netcdf-plugin.zip - no readme
>> geoserver-2.17-RC-ogr-wfs-plugin.zip
>> geoserver-2.17-RC-ogr-wps-plugin.zip
>> geoserver-2.17-RC-oracle-plugin.zip - *GPL and NOTICE not needed*
>> geoserver-2.17-RC-printing-plugin.zip - no readme
>> geoserver-2.17-RC-pyramid-plugin.zip - no readme
>> geoserver-2.17-RC-querylayer-plugin.zip - no readme
>> geoserver-2.17-RC-sldservice-plugin.zip
>> geoserver-2.17-RC-sqlserver-plugin.zip - no readme
>> geoserver-2.17-RC-teradata-plugin.zip
>> geoserver-2.17-RC-vectortiles-plugin.zip - no readme
>> geoserver-2.17-RC-wcs2_0-eo-plugin.zip - no readme
>> geoserver-2.17-RC-web-resource-plugin.zip
>> geoserver-2.17-RC-wps-cluster-hazelcast-plugin.zip - no readme
>> geoserver-2.17-RC-wps-plugin.zip - no readme
>> geoserver-2.17-RC-xslt-plugin.zip - no readme
>> geoserver-2.17-RC-ysld-plugin.zip - no readme
>>
>> --
>> Jody Garnett
>>
>>
>> On Fri, 13 Mar 2020 at 00:25, Jody Garnett <[email protected]>
>> wrote:
>>
>>> Please test out
>>>
>>> https://build.geoserver.org/view/release/job/geoserver-release/271/artifact/distribution/2.17-RC
>>>
>>> And report back, I have made extensive changes to the extensions
>>> (including license files) and docs (producing with maven assembly rather
>>> than zip).
>>>
>>> As such this is both a good use on an RC and an invitation to test with
>>> a bit more caution then usual.
>>> --
>>> --
>>> Jody Garnett
>>>
>> _______________________________________________
> Geoserver-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>


-- 

Regards, Andrea Aime == 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
------------------------------------------------------- *Con riferimento
alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 -
Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni
circostanza inerente alla presente email (il suo contenuto, gli eventuali
allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i
destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per
errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le
sarei comunque grato se potesse darmene notizia. This email is intended
only for the person or entity to which it is addressed and may contain
information that is privileged, confidential or otherwise protected from
disclosure. We remind that - as provided by European Regulation 2016/679
“GDPR” - copying, dissemination or use of this e-mail or the information
herein by anyone other than the intended recipient is prohibited. If you
have received this email by mistake, please notify us immediately by
telephone or e-mail.*
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Reply via email to