[Geoserver-devel] GeoFence dev branch

Hi,
I’m working on a GeoFence issue for which I’ll write a separate email.
This one is about collaboration. I see the master branch is at 3.5-SNAPSHOT
but 3.6.0 is released, and though there’s a 3.5.x branch, there’s no 3.6.x.

So the question is if master should be at 3.6-SNAPSHOT, or a 3.6.x branch should be created.

In any case, can the appropriate branch be created/updated?

TIA

···

Gabriel Roldán

Hi Gabriel,

Please disregard the master branch, since it has been dismissed in favor of main (when you browse to https://github.com/geoserver/geofence, github shows it as default).
Master evolved (with breaking changes for the standalone version) from the 3.4, but it was never used (there are no tags on it). Its “3.5” version in pom file was the next in line version from 3.4, but it was never released.
The “real” (released) 3.5 tags are on main, not master.

About creating new branches: we usually change version number and create a new branch for the previous one when there are somewhat breaking changes (e.g. DTO or major dependency changes).
When there are only fixes we prefer working on the existing branch.

Anway, this mail is just for clarification, since I guess the spotted issue is not a bug at all :slight_smile:

I also reported these info about branches at https://github.com/geoserver/geofence/wiki/GS-GF-Compatibility-matrix#a-note-about-main-and-master-branches

Cheers,
Emanuele

···

Regards,
Emanuele Tajariol

GeoServer Professional Services from the experts!
Visit http://bit.ly/gs-services-us for more information.

Ing. Emanuele Tajariol
Technical Lead

GeoSolutions Group
mobile: +39 347 7895230
office: +39 0584 962313

fax: +39 0584 1660272

https://www.geosolutionsgroup.com/
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.

Hi Emanuele,

thanks a lot, my bad for not noticing.

Cheers,
Gabe

···

Gabriel Roldán