[GeoNode-devel] Python 3 / Django 2 Upgrade version naming and branch
simone.giannecchini at geo-solutions.it
Tue Mar 19 07:05:15 PDT 2019
I fully agree that we should not pollute 2.10, however two things:
-1- it is not clear to me the plan for the two new branches. Are they
expected to merge before 2.11 or after?
-2- Cutting 2.10 now could be too early as there is more clean up that we
might want to do before releasing and this cut would generate a lot of work
now to keep master and 2.10 branches aligned meanwhile.
It would probably be best to have the Python 3 development happen in
parallel in a branch that tracks master and then merge on master at a
certain point when the upgrade is ready or simply have the Python 3 branch
become the new master.
I am also interested to hear what the others think.
Il giorno mar 19 mar 2019 alle 10:03 Alessio Fabiani <
alessio.fabiani at geo-solutions.it> ha scritto:
> Dear devs,
> as the work on upgrading GeoNode 2.10 to Python 3 and Django 2 is moving
> on, I would propose to:
> 1. Create a 2.10 branch which will be used for the next release still
> based on Python 2; this branch will be stable and only major issues will be
> backported until the release
> 2. Move "master" to 2.11; this will be the new development branch still
> based on Python 2
> 3. Create a 2.20 branch which will be the development branch based on
> Any objections? Ideas?
> GeoServer Professional Services from the experts! Visit
> http://goo.gl/it488V for more information.
> Ing. Alessio Fabiani
> Founder/Technical Lead
> GeoSolutions S.A.S.
> Via di Montramito 3/A -
> (LU) - Italy
> phone: +39 0584 962313
> fax: +39 0584 1660272
> mob: +39 331 6233686
> 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.
> geonode-devel mailing list
> geonode-devel at lists.osgeo.org
- sent from my mobile, apologies for brevity and typos-
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the geonode-devel