I would ask that the geonode folks tag the release they need as a patch release (even just to the nexus repo). Depending on a snapshot is a terrible practice, and if you must it should be handled with a git sub module.
The geonetwork folks depend on a snapshot revision be having a git sub module, and building (for example geotools) as part of full build. Jody On Tue, Dec 7, 2021 at 1:31 AM Andrea Aime < andrea.a...@geosolutionsgroup.com> wrote: > Hi, > here is a topic for today's PSC meeting (not feeling all that well, might > not make it to the meeting). > > In GeoSolutions we found that we need to run custom builds of the 2.18.x > series, mostly because of its relationship with GeoNode. GeoNode tends to > stay a little behind in terms of GeoServer version, e.g., the latest > release uses 2.19.x, but the release before is still quite commonly > installed. In addition, they don't typically use public releases, but > snapshots with the exact set of fixes and improvements they need. > > I was wondering, would it be possible to keep the old maintenance series > builds going for another six months, after we stop making releases? > I don't think the extra CPU usage would be unreasonable, and the storage > would be the same, > if you check, we still have 2.16.x nightlies on the build server: > https://build.geoserver.org/geoserver/ > > Cheers > Andrea > > > == > GeoServer Professional Services from the experts! > > Visit http://bit.ly/gs-services-us for more information. > == > > Ing. Andrea Aime > @geowolf > Technical Lead > > GeoSolutions Group > phone: +39 0584 962313 > > fax: +39 0584 1660272 > > mob: +39 333 8128928 > > https://www.geosolutionsgroup.com/ > > http://twitter.com/geosolutions_it > > ------------------------------------------------------- > > 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. > > 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 > _______________________________________________ > Geoserver-devel mailing list > Geoserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-devel > -- -- Jody Garnett
_______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
