[GeoNode-devel] [GeoNode-users] GeoNode versions and branches

Ariel Nunez ingenieroariel at gmail.com
Tue May 16 06:12:11 PDT 2017


Thanks Alessio for taking the lead of organizing the branches for the
release. I agree that the notifications work has a steep integration
curve and it makes sense to leave it for a latter release.

On Tue, May 16, 2017 at 3:18 AM, Alessio Fabiani
<alessio.fabiani at geo-solutions.it> wrote:
> Dear all,
> I'm going to start this thread in order to summarize a bit the status of
> GeoNode branches and current versions.
>
> 2.6rc1
> =================
> This is a stable version candidate for the release, which will happen during
> this week.
> On GitHub this is related to the branch 2.6.x
> GeoNode 2.6 works against GeoServer 2.9 with OAuth2 authentication
>
> master and 2.7.x
> =================
> At the time I'm writing this email, those two are aligned.
> 2.7.x will become the new stable branch right after the release. A sort of
> soft-freeze of master features, where only approved improvements and
> bug-fixes related to Issues and PRs will be backported.
>
> "master" (which currently is GeoNode 2.7.x) works against GeoServer 2.10
> with OAuth2 authentication
>
> WARNING: The old master branch has been switched to "notifications" one. In
> order to re-align your code you can either:
>
> 1. Do a fresh checkout
> 2. Follow the instructions below
>
> # re-align branches
> git branch -f new_name HEAD
> git checkout new_name
> git branch --set-upstream-to=origin/new_name new_name
> git push --set-upstream origin new_name
> git pull
>
>
> notifications
> =================
> This branch is aligned with the old "master" branch and contains a work
> (almost ready) allowing GeoNode to enable an external broker for
> notifications and signals. This is an important step toward an Enterprise
> version of GeoNode, moving it a step forward with:
>
> 1. Advanced monitoring and alerting features
> 2. Clustering and multi-tenancy capabilities
> 3. Cloud-ready component
>
> Best Regards,
> Alessio Fabiani.
>
> ==
> GeoServer Professional Services from the experts!
> Visit http://goo.gl/it488V for more information.
> ==
>
> Ing. Alessio Fabiani
> @alfa7691
> github
> 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-users mailing list
> geonode-users at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/geonode-users
>


More information about the geonode-devel mailing list