[GeoNode-devel] Which GeoServer version we should use (i.e. nightlies VS releases)
ortelius at gmail.com
Fri Jul 31 11:20:23 PDT 2015
This makes sense. +1
On Friday, July 31, 2015, Simone Giannecchini <
simone.giannecchini at geo-solutions.it> wrote:
> Dear All,
> recently I have been discussing with other devs about which GS version
> we should depend onto in GeoNode.
> As you might know GeoServer has, at all times, 3 active branches:
> - Master (2.8.x at this stage) which is open for development and is
> considered unstable
> - Stable (2.7.x now) which get minor developments + bug fixes
> - Maintenance (2.6.x now) which gets only bug fixes
> GS has a time-boxed release model so we more or less know when a
> release for a certain branch will be made.
> Generally speaking (at least IMHO) for a project like GN it is good to
> depend on the stable branch. Master would be dangerous, Maintenance
> could be moving too slow (but still an option).
> So yeah, that's fine we are already doing that. The point is what to
> do when we cut a GN release? Do we use a GS nightly ( they are all
> marked clearly and then we can track it easily)? Do we only use
> The obvious answer is to use releases from the stable branch and make
> everybody happy. There is one problem though unless we align with the
> GS releases we might have problem with doing GS bugfixes before a GN
> Let's talk about present times. Right now we are depending on 2.7.x
> nightly, so if there's something bugging us in GS we fix it and the
> day after we get the fix in GN. If on September 1st we want to release
> GN 2.4 we won't have a GS release to use because 2.7.3 will be out in
> October, hence we either wait or we ask the GeoServer community to
> make an intermediate release (e.g. 188.8.131.52).
> My proposal is as follows:
> - try to track geoserver stable nightly in GN development
> - tentatively align GN release to GS releases (they are done pretty
> often anyway)
> - if we want to do a GN release and we can't wait for a GS one, we ask
> the GS community to cut an intermediate release
> I already started a similar discussion on the GS mailing asking for
> opinions on this approach :)
> Simone Giannecchini
> GeoServer Professional Services from the experts!
> Visit http://goo.gl/it488V for more information.
> Ing. Simone Giannecchini
> GeoSolutions S.A.S.
> Via Poggio alle Viti 1187
> 55054 Massarosa (LU)
> phone: +39 0584 962313
> fax: +39 0584 1660272
> mob: +39 333 8128928
> 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
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the geonode-devel