[GeoNode-devel] Time to do a Beta and a Release

Jeffrey Johnson ortelius at gmail.com
Fri Sep 25 07:00:39 PDT 2015


I believe so. Daniel, if you can make the releases to Pypi, please go for
it. Otherwise we may need help from Ariel.

On Fri, Sep 25, 2015 at 6:59 AM, Alessio Fabiani <
alessio.fabiani at geo-solutions.it> wrote:

> Yes IMHO
>
> -A.
>
> ==
> GeoServer Professional Services from the experts! Visit
> http://goo.gl/NWWaa2 for more information.
> ==
>
> Ing. Alessio Fabiani
> @alfa7691
> Founder/Technical Lead
>
> GeoSolutions S.A.S.
> Via Poggio alle Viti 1187
> 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.
>
> On Fri, Sep 25, 2015 at 3:57 PM, Daniel Berry <dberry at boundlessgeo.com>
> wrote:
>
>> In regards to the gsimporter and gsconfig are we at a point where we can
>> update pypi.
>>
>>
>> I loaded both on testpypi
>>
>> gsimporter - https://testpypi.python.org/pypi/gsimporter/0.2
>> gsconfig - https://testpypi.python.org/pypi/gsconfig/0.6.14
>>
>> Dan
>>
>> On Fri, Sep 25, 2015 at 4:04 AM, Paolo Corti <pcorti at gmail.com> wrote:
>>
>>> Hi Alessio
>>>
>>> >
>>> > On Fri, Sep 25, 2015 at 10:39 AM, Paolo Corti <pcorti at gmail.com>
>>> wrote:
>>> >>
>>> >> I agree to start releasing a new beta (beta 27) and maybe start
>>> >> thinking about releasing a RC1 (time is short to the sprint).
>>> >>
>>> >> By the way: I see several issues still open regarding GeoServer
>>> >> integration [1], maybe it would be great to do a triage to check what
>>> >> it was fixed and what it was not.
>>> >> Personally I see #2177 as a blocker to move our production to GS 2.7.
>>> >
>>> >
>>> > I did not have the chance to look deeply in to this yet, but at a first
>>> > glance I'm not fully sure this depends on GS. It seems to be more an
>>> issue
>>> > on GeoNode side. Do you have any more details? In any case I'll try to
>>> find
>>> > some time to inspect this issue as soon as possible. (Also, make a try
>>> using
>>> > the very latest versions of gsconfig and gsimporter, the communication
>>> > between the client and GeoServer has several fixes and improvements
>>> which
>>> > maybe already fixed this issue too)
>>> >
>>>
>>> we can look into this at the sprint, and yes you are correct, it is
>>> just Django, sorry for the confusion.
>>>
>>> >>
>>> >>
>>> >> Is the SQL security backend correctly working with GS 2.7 [2]?
>>> >
>>> >
>>> > Never tested. Can you please send me few lines and details in order to
>>> test
>>> > and troubleshoot this?
>>> >
>>>
>>>
>>> http://docs.geonode.org/en/dev/deploy/production.html#installing-the-stored-procedure
>>>
>>> hope it helps
>>> cheers
>>> p
>>>
>>> --
>>> Paolo Corti
>>> Geospatial software developer
>>> web: http://www.paolocorti.net
>>> twitter: @capooti
>>> skype: capooti
>>> _______________________________________________
>>> geonode-devel mailing list
>>> geonode-devel at lists.osgeo.org
>>> http://lists.osgeo.org/cgi-bin/mailman/listinfo/geonode-devel
>>>
>>
>>
>>
>> --
>> *Daniel Berry*
>> Professional Services Engineer | Boundless
>> dberry at boundlessgeo.com
>> 512-468-3946 (cell)
>> @boundlessgeo
>>
>>
>
> _______________________________________________
> geonode-devel mailing list
> geonode-devel at lists.osgeo.org
> http://lists.osgeo.org/cgi-bin/mailman/listinfo/geonode-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geonode-devel/attachments/20150925/334ce02f/attachment-0001.html>


More information about the geonode-devel mailing list