<div dir="auto">+1<div dir="auto">I think this will work perfectly</div><div dir="auto">Cheers</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Mar 21, 2019, 13:18 Francesco Bartoli <<a href="mailto:xbartolone@gmail.com">xbartolone@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div name="messageBodySection" style="font-size:14px;font-family:-apple-system,BlinkMacSystemFont,sans-serif">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.
<div><br></div>
<div>My +1</div>
</div>
<div name="messageSignatureSection" style="font-size:14px;font-family:-apple-system,BlinkMacSystemFont,sans-serif"><br>
Francesco</div>
<div name="messageReplySection" style="font-size:14px;font-family:-apple-system,BlinkMacSystemFont,sans-serif">Il 21 mar 2019, 18:09 +0100, Simone Giannecchini <<a href="mailto:simone.giannecchini@geo-solutions.it" target="_blank" rel="noreferrer">simone.giannecchini@geo-solutions.it</a>>, ha scritto:<br>
<blockquote type="cite" style="margin:5px 5px;padding-left:10px;border-left:thin solid #1abc9c">
<div dir="ltr">
<div>Dear Angelos, Dear Jeremiah,</div>
<div>we discussed a bit internally and here is our proposal (that extends yours):</div>
<div><br></div>
<div>- We would want to cut branch 2.10 in proximity of the summit for doing the release there. This release is for Python 2.</div>
<div>- 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.</div>
<div><br></div>
<div>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.</div>
<div><br></div>
<div>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. </div>
<div><br></div>
<div>
<div dir="ltr" class="m_-1026430051222780190gmail-m_-3406389929895585802gmail-m_-5605460494862988165m_-5688747094735172861gmail_signature">
<div dir="ltr">
<div>Regards,<br></div>
</div>
</div>
</div>
<div>
<div dir="ltr" class="m_-1026430051222780190gmail-m_-3406389929895585802gmail_signature">
<div dir="ltr">
<div>Simone Giannecchini</div>
</div>
</div>
</div>
<div>
<div dir="ltr" class="m_-1026430051222780190gmail_signature" data-smartmail="gmail_signature">
<div dir="ltr">
<div>==<br>
GeoServer Professional Services from the experts!<br>
Visit <a href="http://bit.ly/gs-services" target="_blank" rel="noreferrer">http://bit.ly/gs-services</a> for more information.<br>
==<br>
Ing. Simone Giannecchini<br>
@simogeo<br>
Founder/Director<br>
<br>
GeoSolutions S.A.S.<br>
Via di Montramito 3/A<br>
55054 Massarosa (LU)<br>
Italy<br>
phone: +39 0584 962313<br>
fax: +39 0584 1660272<br>
mob: +39 333 8128928<br>
<br>
<a href="http://www.geo-solutions.it" target="_blank" rel="noreferrer">http://www.geo-solutions.it</a><br>
<a href="http://twitter.com/geosolutions_it" target="_blank" rel="noreferrer">http://twitter.com/geosolutions_it</a><br>
<br>
-------------------------------------------------------<br>
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.<br>
<br>
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.</div>
</div>
</div>
</div>
<br></div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, Mar 21, 2019 at 6:02 PM Jeremiah Cooper <<a href="mailto:jcooper@jeremiahcooper.com" target="_blank" rel="noreferrer">jcooper@jeremiahcooper.com</a>> wrote:<br></div>
<blockquote class="gmail_quote" style="margin:5px 5px;padding-left:10px;border-left:thin solid #e67e22">+1 to the plan Angelos laid out. Makes sense to me.<br>
<br>
Thanks.<br>
<br>
Jeremiah Cooper<br>
<br>
On Thu, Mar 21, 2019 at 12:51 PM Angelos Tzotsos <<a href="mailto:gcpp.kalxas@gmail.com" target="_blank" rel="noreferrer">gcpp.kalxas@gmail.com</a>> wrote:<br>
><br>
> Hi all,<br>
><br>
> After some discussion on Gitter, here is another proposal:<br>
><br>
> 1. Create a 2.10.x branch to work on finalizing 2.10 release<br>
><br>
> 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.<br>
><br>
> 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.<br>
><br>
> 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.<br>
><br>
> Thoughts?<br>
><br>
> Cheers,<br>
> Angelos<br>
><br>
> On 3/19/19 11:52 AM, Alessio Fabiani wrote:<br>
><br>
> Dear devs,<br>
> as the work on upgrading GeoNode 2.10 to Python 3 and Django 2 is moving<br>
> on, I would propose to:<br>
><br>
> 1. Create a 2.10 branch which will be used for the next release still based<br>
> on Python 2; this branch will be stable and only major issues will be<br>
> backported until the release<br>
><br>
> 2. Move "master" to 2.11; this will be the new development branch still<br>
> based on Python 2<br>
><br>
> 3. Create a 2.20 branch which will be the development branch based on<br>
> Python3<br>
><br>
> Any objections? Ideas?<br>
><br>
> Regards,<br>
> Alessio.<br>
><br>
><br>
><br>
> _______________________________________________<br>
> geonode-devel mailing list<br>
> <a href="mailto:geonode-devel@lists.osgeo.org" target="_blank" rel="noreferrer">geonode-devel@lists.osgeo.org</a><br>
> <a href="https://lists.osgeo.org/mailman/listinfo/geonode-devel" rel="noreferrer noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/geonode-devel</a><br>
><br>
><br>
><br>
> --<br>
> Angelos Tzotsos, PhD<br>
> Charter Member<br>
> Open Source Geospatial Foundation<br>
> <a href="http://users.ntua.gr/tzotsos" rel="noreferrer noreferrer" target="_blank">http://users.ntua.gr/tzotsos</a><br>
><br>
> _______________________________________________<br>
> geonode-devel mailing list<br>
> <a href="mailto:geonode-devel@lists.osgeo.org" target="_blank" rel="noreferrer">geonode-devel@lists.osgeo.org</a><br>
> <a href="https://lists.osgeo.org/mailman/listinfo/geonode-devel" rel="noreferrer noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/geonode-devel</a><br>
_______________________________________________<br>
geonode-devel mailing list<br>
<a href="mailto:geonode-devel@lists.osgeo.org" target="_blank" rel="noreferrer">geonode-devel@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/geonode-devel" rel="noreferrer noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/geonode-devel</a><br></blockquote>
</div>
_______________________________________________<br>
geonode-devel mailing list<br>
<a href="mailto:geonode-devel@lists.osgeo.org" target="_blank" rel="noreferrer">geonode-devel@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/geonode-devel" target="_blank" rel="noreferrer">https://lists.osgeo.org/mailman/listinfo/geonode-devel</a><br></blockquote>
</div>
</div>
_______________________________________________<br>
geonode-devel mailing list<br>
<a href="mailto:geonode-devel@lists.osgeo.org" target="_blank" rel="noreferrer">geonode-devel@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/geonode-devel" rel="noreferrer noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/geonode-devel</a><br>
</blockquote></div>