[Geoserver-devel] proposed date: bug stomp and 2.11-RC release

GeoServer GeoServer Developer
1

I am sorry I was unable to attend last weeks meeting; there are a couple agenda items I wanted to cover - can we do so now in email.

Bug Stomp Feb 24th → March 6th

We missed doing a bug stomp last week (sorry I was travelling).

I am aware that we are already asking for a lot of volunteer time for the code-sprint at the end of the month., however I would really like to ensure we do a bug stomp during the beta / RC1 timeframe.

Can I propose March 10th as a replacement “bug stomp” day.

GeoServer 2.11-RC March 3rd → March 8th

If nobody has volunteered to make the 2.11-RC this friday, I am willing to do so … anytime after the bug stomp.

I know this would stretch out the code-freeze - so we would all need to be okay with that?

···

–
Jody Garnett

2

*Bug Stomp Feb 24th --> March 6th*

We missed doing a bug stomp last week (sorry I was travelling).

I am aware that we are already asking for a lot of volunteer time for the
code-sprint at the end of the month., however I would really like to ensure
we do a bug stomp during the beta / RC1 timeframe.

Can I propose March 10th as a replacement "bug stomp" day.

Correction - can I propose the bug stomp March 6th (so we fix some bugs
prior to issuing RC).

3

March 6th works for me.

Cheers
Andrea

···

On Wed, Mar 1, 2017 at 3:16 AM, Jody Garnett <jody.garnett@anonymised.com…403…> wrote:

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
Geoserver-devel@anonymised.com.366…sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

–

Bug Stomp Feb 24th → March 6th

We missed doing a bug stomp last week (sorry I was travelling).

I am aware that we are already asking for a lot of volunteer time for the code-sprint at the end of the month., however I would really like to ensure we do a bug stomp during the beta / RC1 timeframe.

Can I propose March 10th as a replacement “bug stomp” day.

Correction - can I propose the bug stomp March 6th (so we fix some bugs prior to issuing RC).

==
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.