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

Thu Mar 21 16:47:52 PDT 2019

+1
I think this will work perfectly
Cheers

On Thu, Mar 21, 2019, 13:18 Francesco Bartoli <xbartolone at gmail.com> wrote:

> I like the proposal from Angelos and I don’t have any concern about the
> extension from GeoSolutions to wait the summit for 2.10.
>
> My +1
>
> Francesco
> Il 21 mar 2019, 18:09 +0100, Simone Giannecchini <
> simone.giannecchini at geo-solutions.it>, ha scritto:
>
> Dear Angelos, Dear Jeremiah,
> we discussed a bit internally and here is our proposal (that extends
> yours):
>
> - We would want to cut branch 2.10 in proximity of the summit for doing
> the release there. This release is for Python 2.
> - The new master is open for merging the work on Python 3 once the work si
> ready and reviewed. I would expect porting over the work will take a little
> since it will have to undergo some review by the community. This would
> become GeoNode 3.
>
> Notice that there is some additional clean up that we might want to
> perform before 2.10 based on feedback from clients on old things that don't
> work properly (e.g. GeoNetwork integration) hence this is why we would want
> to wait a little for 2.10 to be cut.
>
> As far as the Python 3 work is concerned, with this plan Jeremiah you
> would need to work on a fork that follow current master and then after 2.10
> is out we start the process to review and merge. We plan to help out with
> this merge process, obviously, as this Python 3 upgrade is strategic.
>
> Regards,
> Simone Giannecchini
> ==
> GeoServer Professional Services from the experts!
> Visit http://bit.ly/gs-services for more information.
> ==
> Ing. Simone Giannecchini
> @simogeo
> Founder/Director
>
> GeoSolutions S.A.S.
> Via di Montramito 3/A
> 55054  Massarosa (LU)
> Italy
> phone: +39 0584 962313
> fax:     +39 0584 1660272
> mob:   +39  333 8128928
>
> 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.
>
>
> On Thu, Mar 21, 2019 at 6:02 PM Jeremiah Cooper <
> jcooper at jeremiahcooper.com> wrote:
>
>> +1 to the plan Angelos laid out.  Makes sense to me.
>>
>> Thanks.
>>
>> Jeremiah Cooper
>>
>> On Thu, Mar 21, 2019 at 12:51 PM Angelos Tzotsos <gcpp.kalxas at gmail.com>
>> wrote:
>> >
>> > Hi all,
>> >
>> > After some discussion on Gitter, here is another proposal:
>> >
>> > 1. Create a 2.10.x branch to work on finalizing 2.10 release
>> >
>> > 2. Move master to version 2.99 and start merging work related to Python
>> 3 and Django 2 which will become GeoNode 3.0 (easier to communicate to
>> users and organizations). GeoNode 3.0 will be Python 3 only.
>> >
>> > 3. Anything related to Python 2 stays on GeoNode 2.x and we leave room
>> for potential 2.12 release after some time if needed.
>> >
>> > 4. Future plans for GeoNode, like work on geonode-api and separation of
>> UI etc can then become GeoNode 4.0 which probably will be a re-write. This
>> also is lines up with CSW 4.0 version number which will be based on OpenAPI
>> and new OGC OWS direction.
>> >
>> > Thoughts?
>> >
>> > Cheers,
>> > Angelos
>> >
>> > On 3/19/19 11:52 AM, Alessio Fabiani wrote:
>> >
>> > 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.
>> >
>> >
>> >
>> > _______________________________________________
>> > geonode-devel mailing list
>> > geonode-devel at lists.osgeo.org
>> > https://lists.osgeo.org/mailman/listinfo/geonode-devel
>> >
>> >
>> >
>> > --
>> > Angelos Tzotsos, PhD
>> > Charter Member
>> > Open Source Geospatial Foundation
>> > http://users.ntua.gr/tzotsos
>> >
>> > _______________________________________________
>> > geonode-devel mailing list
>> > geonode-devel at lists.osgeo.org
>> > https://lists.osgeo.org/mailman/listinfo/geonode-devel
>> _______________________________________________
>> geonode-devel mailing list
>> geonode-devel at lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/geonode-devel
>>
> _______________________________________________
> geonode-devel mailing list
> geonode-devel at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/geonode-devel
>
> _______________________________________________
> geonode-devel mailing list
> geonode-devel at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/geonode-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geonode-devel/attachments/20190321/41c444fa/attachment.html>