[Geotools-devel] Reminder: GeoTools / GeoServer meeting at 19:30 UTC on Tuesday

2017-10-30 Thread Ben Caradoc-Davies 

GeoTools / GeoServer committee meeting on Skype at 19:30 UTC on Tuesday:
https://www.timeanddate.com/worldclock/fixedtime.html?msg=GeoTools+/+GeoServer+Meeting=2017=10=31=19=30=0=1

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] [Geoserver-devel] Who force pushed to 2.12.x?

2017-10-30 Thread Ben Caradoc-Davies 
No problem, Alessio. You are not the first (or even the third) to 
force-push, and we now have the safety catch we need: branch protection.


There are five commits of yours that were on 2.12.x but were removed by 
your force push and have not yet been restored. I do not have these 
commits, and I was not sure if you removed any of these intentionally. 
Conveniently, these five commits are listed in a single Jenkins job:

https://build.geoserver.org/view/geoserver/job/geoserver-2.12.x/37/changes

Please review these missing commits and apply those that you would like 
to keep to the 2.12.x branch.


Kind regards,
Ben.

On 30/10/17 22:03, Alessio Fabiani wrote:

It seems it was my fault. I only remember to have reverted a wrong commit,
did not want to do a push force. It was a mistake.

Protecting branches for sure is the best way to avoid similar mistakes in
the future. Please let me know if I can do something else.

Regards,

Alessio Fabiani

==
GeoServer Professional Services from the experts! Visit http://goo.gl/it488V
for more information.
==

Ing. Alessio Fabiani

@alfa7691
Founder/Technical Lead


GeoSolutions S.A.S.
Via di Montramito 3/A
55054  Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob:   +39 331 6233686

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.

On Sun, Oct 29, 2017 at 12:05 AM, Ben Caradoc-Davies 
wrote:


On 29/10/17 01:50, Andrea Aime wrote:


On Sat, Oct 28, 2017 at 1:43 PM, Ben Caradoc-Davies 
wrote:


I have also enabled basic branch protection on all GeoTools release
branches (same as master). This prevents force pushes and deletion of
these
branches.


Awesome, thanks for doing that.


Yes, this should be part of our RC-release-create-new-stable-branch
procedure for GeoTools and GeoServer. Branching is still a manual step so
this will be as well. For example:
http://docs.geotools.org/latest/developer/procedures/release
.html#if-you-are-cutting-the-first-rc-of-a-series-create-the
-stable-branch


Yep, agreed it should be part of the release process.



Done.


Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel





--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel