[GeoNode-devel] [GeoNode-users] ATTENTION: GeoNode GitHub Repos Summary and Status

Wed Apr 25 14:07:35 PDT 2018

Hi Alessio

thanks so much for the explanation.

I think it is very useful to have these notes in the wiki and keep
updated with any future changes, therefore I have created a wiki page
here "For Developers":
https://github.com/GeoNode/geonode/wiki/For-Developers

We can include more stuff "for developers" within the same page. For
example code style guidelines, pull request submission instructions, etc...

best
Paolo

On Tue, Apr 24, 2018 at 3:52 AM, Simone Dalmasso
<simone.dalmasso at gmail.com> wrote:
> Thanks a lot Alessio for sharing it!
>
> Great job.
>
> 2018-04-24 0:56 GMT+02:00 Olivier Dalang <olivier.dalang at gmail.com>:
>>
>> Hi !
>>
>> Thank you very much Alessio for the clarifications, it's very helpful.
>>
>> Could expand a little on the branches description by explaining the policy
>> for each branch (including the 2.6.x branch) :
>>
>> - what is accepted in the branch (breaking changes, new features, bugfixes
>> only, nothing...)
>> - ETA and/or conditions for release
>> - expected lifetime after which the branch won't have new releases
>>
>> Compared to semantic versioning (major.minor.patch, corresponding to
>> breaking-changes/non-breaking-changes/bugfixes), I think currently use an
>> additional top level but without no patch level
>> (complete-rewrites.major.minor).
>>
>> This is a bit hard to work with if you need stable branches. For example,
>> if you're using 2.8.0 and need the bugfixes, you'll have to wait for 2.8.1,
>> but it will also include new features (and hence new bugs, database
>> migrations, etc...).
>>
>> I suggest adding a new version level for patch versions, so that we have
>> actually stable branches. This clearly represents a little bit additional
>> work, but I believe if policies are very clear, the community would be able
>> to do the work of backporting the bugfixes they need if they know there's
>> going to be a release soon. Also we can do that only for a few select
>> branches (that are LTS).
>>
>> Note that I don't say we should do strict semantic versioning (maybe a bit
>> difficult), my main concern is separating new features and bug fixes.
>>
>>
>> And by the way, if 2.7.x is the release candidate for 2.8.1, can't we just
>> call it 2.8.x ? (kind of counter intuitive to have 2.7.x ahead of 2.8.0)
>>
>>
>> Thanks for the great work !!
>>
>> Olivier
>>
>>
>>
>>
>>
>>
>> On Mon, Apr 23, 2018 at 11:15 PM, Alessio Fabiani
>> <alessio.fabiani at geo-solutions.it> wrote:
>>>
>>> Dear all, please read carefully here below.
>>>
>>> You can find here the list and status of GeoNode GitHub current branched
>>> updated @ 23rd April 2018
>>>
>>> 2.8.0
>>> ====
>>>
>>> https://github.com/GeoNode/geonode/tree/2.8.0
>>>
>>>
>>> - Based on Django 1.8.19 and Celery 4.1.0
>>> - Compatible with Ubuntu 16.0.4 and CentOS 7 (the only ones officially
>>> tested currently)
>>>
>>> NOTES: This branch is frozen and contains everything until latest stable
>>> GeoNode release 2.8.0. This branch won't be changed until the next release
>>> for the 2.8.0 train (2.8.1).
>>>
>>> At that point the source code of GeoNode 2.8.0 will be found only on 2.8
>>> tag
>>>
>>> https://github.com/GeoNode/geonode/releases/tag/2.8
>>>
>>> 2.7.x
>>> ====
>>>
>>> https://github.com/GeoNode/geonode/tree/2.7.x
>>>
>>> - Based on Django 1.8.19 and Celery 4.1.0
>>> - Compatible with Ubuntu 16.0.4 and CentOS 7 (the only ones officially
>>> tested currently)
>>>
>>> NOTES: This branch is the GeoNode 2.8.1 release candidate. Currently
>>> marked as 2.7.7 version, before the official release process you will be
>>> able to find 2.7.7+ deb packages on unstable ppa.
>>>
>>> 2.7.x train will remain based on Django 1.8 forever
>>>
>>>
>>> 2.9.x/master
>>> ==========
>>>
>>> https://github.com/GeoNode/geonode
>>>
>>> - Based on Django 1.11.11 and Celery 4.1.0
>>>
>>> - Still under testing. This is meant to be working with latest
>>> Ubuntu/CentOS releases
>>>
>>> NOTES: This branch is the GeoNode 2.10.0 candidate.  Currently marked as
>>> 2.9.0 version, before the official release process you will be able to find
>>> 2.9.0+ deb packages on unstable ppa.
>>>
>>> 2.9.x train will remain based on Django 1.11 forever
>>>
>>>
>>>
>>> Regards,
>>>
>>> Alessio Fabiani
>>>
>>> ==
>>> 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
>>>
>>> -------------------------------------------------------
>>>
>>> AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
>>>
>>> Le informazioni contenute in questo messaggio di posta elettronica e/o
>>> nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro
>>> utilizzo è consentito esclusivamente al destinatario del messaggio, per le
>>> finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio
>>> senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia
>>> via e-mail e di procedere alla distruzione del messaggio stesso,
>>> cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo
>>> anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per
>>> finalità diverse, costituisce comportamento contrario ai principi dettati
>>> dal D.Lgs. 196/2003.
>>>
>>> The information in this message and/or attachments, is intended solely
>>> for the attention and use of the named addressee(s) and may be confidential
>>> or proprietary in nature or covered by the provisions of privacy act
>>> (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
>>> Code).Any use not in accord with its purpose, any disclosure, reproduction,
>>> copying, distribution, or either dissemination, either whole or partial, is
>>> strictly forbidden except previous formal approval of the named
>>> addressee(s). If you are not the intended recipient, please contact
>>> immediately the sender by telephone, fax or e-mail and delete the
>>> information in this message that has been received in error. The sender does
>>> not give any warranty or accept liability as the content, accuracy or
>>> completeness of sent messages and accepts no responsibility  for changes
>>> made after they were sent or for other risks which arise as a result of
>>> e-mail transmission, viruses, etc.
>>>
>>>
>>> _______________________________________________
>>> 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
>>
>
>
>
> --
> Simone
>
> _______________________________________________
> geonode-users mailing list
> geonode-users at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/geonode-users
>

-- 
Paolo Corti
Geospatial software developer
web: http://www.paolocorti.net
twitter: @capooti
skype: capooti