Assembling the state of geoserver slides really showed me how little time
is left, and how much functionality is trying to make that code freeze
deadline.
Examples: such as hue rotate (which may need a proposal), Kevin has a GWC
security proposal as well. There is also some flat out work to do such as
the GWC rest api migration.
The other factor is foss4g is landing right at the cut off date effective
cut off date is even earlier. If more changes come in it will be a
challenge to review them that week.
I also feel bad in that Torben and I ran forward the wiki release schedule
in the July 27 meeting to facilitate planning - and made a mistake -
showing the code freeze in September. So I feel I have personally made this
timing worse :(
--
Jody Garnett
On 14 July 2017 at 02:55, Andrea Aime <[email protected]> wrote:
> Hi Jody,
> so you foresee another rush of last minute changes right before the
> beta release? Keeping the schedule as is should avoid that (as in, either
> stuff is in by mid August, or you're lost the train).
>
> Cheer
> Andrea
>
> On Thu, Jul 13, 2017 at 7:22 PM, Jody Garnett <[email protected]>
> wrote:
>
>> I noticed the wiki was inconsistent on release schedule dates
>> <https://github.com/geoserver/geoserver/wiki/Release-Schedule> and have
>> now corrected:
>>
>> DateGeoToolsGeoServerGWCResponsibleNote
>> 2017-09-18 18.0 2.12 1.12 stable release
>> 2017-09-04 18.0-RC1 2.12-RC1 1.12-RC1 release candidate
>> 2017-08-21 18.0-beta 2.12-beta 1.12-beta beta release / code freeze
>> 2017-08-21 16.5 2.10.5 1.10.5 final maintenance release
>>
>> This is awkward timing with foss4g, could I suggest we move the release
>> candidate back a week because of the conference.
>>
>> * 2017-08-28 beta release and code freeze
>> * 2017-09-11 release candidate
>> * 2017-09-18 release
>>
>> This would allow us to still hit our release goal, by reducing the time
>> between the release candidate and the release :(
>>
>> --
>> Jody Garnett
>>
>> ------------------------------------------------------------
>> ------------------
>> 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
>>
>>
>
>
> --
>
> 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 <+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
