[GeoNode-devel] Python 3 / Django 2 Upgrade version naming and branch

Alessio Fabiani alessio.fabiani at geo-solutions.it
Tue Mar 19 07:29:54 PDT 2019


Hello Simone and Francesco,
just to clarify a bit more, the idea would be to following one.

When we are ready to start the release process (**after** clean up and
other preparation stuff we have already discussed at the meeting), the 2.10
branch would become the new stable branch, where we backport only critical
issues and/or features the community has tested enough (and that have a
maintainer).

The 2.11 branch would become the Python 2 dev branch for a while until we
definitively switch to Python 3. This because of people that installed
2.10, might still need to backport fixes without being forced to switch to
Python 3 and Django 2.

In the meantime, we will align the branches with the 2.20 one, based on
Python 3, and once we are ready to switch definitively, the next releases
will be based on the latter.

In parallel, hopefully, the work on GeoNode 3 will move on.



Il giorno mar 19 mar 2019 alle ore 15:05 Simone Giannecchini <
simone.giannecchini at geo-solutions.it> ha scritto:

> Hi Alessio,
> 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.
>
> Regards,
> Simone.
> 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
>> Python3
>>
>> Any objections? Ideas?
>>
>> Regards,
>> Alessio.
>>
>>
>> --
>>
>> ==
>>
>> 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 -
>> <https://maps.google.com/?q=Via+di+Montramito+3/A+-++55054+%C2%A0Massarosa&entry=gmail&source=g>55054
>>  Massarosa
>> <https://maps.google.com/?q=Via+di+Montramito+3/A+-++55054+%C2%A0Massarosa&entry=gmail&source=g>
>> (LU) - Italy
>> phone: +39 0584 962313
>> fax:     +39 0584 1660272
>> mob:   +39 331 6233686
>>
>>
>> http://www.geo-solutions.it
>> 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.
>> _______________________________________________
>> geonode-devel mailing list
>> geonode-devel at lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/geonode-devel
>>
> --
> Regards,
> Simone Giannecchini.
> GeoSolutions Director
>
> - sent from my mobile, apologies for brevity and typos-
>


-- 

==

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

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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geonode-devel/attachments/20190319/3bcf2b46/attachment-0001.html>


More information about the geonode-devel mailing list