On Sat, Oct 28, 2017 at 1:43 PM, Ben Caradoc-Davies <ben@anonymised.com>
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.
Cheers
Andrea
--
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
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.
Looking in github it looks like it was used in the past: master, and branches 2.5.x - 2.8.x are protected but no others are. Probably a useful thing to add to the process when creating a new maintenance branch would be to go into GitHub and add that branch as a protected one. It looks like it is possible to do it via the GitHub api as well, so also possible to add to the release scripts as well.