Fair enough. I will say that I have to do the back port regardless for a project but I can easily work from a branch in my own fork for now if folks decide it’s not worth the risk.
As for mitigating the risk, your suggestions all sound good. Regarding updating a demo server the only people I know that run a stable GeoServer demo are Boundless and GeoSolutions. So I’ll let those devs comment on if they want to do an upgrade. I can cut a 2.8.x build with the library upgrades or they can grab a nightly from master. Just let me know. As for running benchmarks is there a test suite that is readily available and easy to set up? Depending on how much work is involved there I can volunteer some time to put to that. As for a milestone release from master I can also put some time toward that as long as it’s something I can bust off in a few hours time frame. If there is going to be more ceremony around it not sure how much time I can devote to it at the moment. On Fri, Nov 27, 2015 at 2:46 AM Andrea Aime <andrea.a...@geo-solutions.it> wrote: > Hi Justin, > this one had me thinking a while :-) > > So, there are two separate things. The first one is the Spring upgrade. > It's an upgrade between > two minor versions, had a single commit, basically just the version number > change in the pom files, worked fine. > The Spring integration is exercised by our tests and by the CITE tests, > all of them seem to be working fine. > An upgrade of the library that wires everything is still risky, but given > the above I'm not too concerned... let's make that a +0? > > I believe the Jetty upgrade is more contentious, more reward and more risk. > The Jetty we are shipping with on 2.8.x is a bit of an horror, old, > inefficient, with known security risks, so an > upgrade is very much welcomed. > Testing wise however we are coming out pretty light though. We had the > CITE tests running on master for a few > days, and I believe some people tested it interactively... but the stable > series is meant for production, so I believe > we need more than that. > And then we have the installers: how many people have tried the windows > and OSX installer with the new Jetty and can attest they are working? > Possibly a number <= 1, assuming Justin has had the time to check both > when making the Jetty upgrade :-p > > So... from this point of view I'd be -1 on the Jetty upgrade, but at the > same time... it would be so good... > so what can be done to mitigate those risks? > Here is a few of ideas, hopefully others will add more/better ones: > * Have a well known demo instance of GeoServer somewhere use the new bin > package and see how it stands the load > * We could run some of the benchmarking exercises on top of it > * To have people use the installers, maybe cut a milestone release out of > trunk? We have a few new features > already in there to sweeten the pot and make it more interesting for > people to kick its tires > > What do you think? > > Cheers > Andrea > > > > On Thu, Nov 26, 2015 at 6:25 PM, Justin Deoliveira <jdeol...@gmail.com> > wrote: > >> Hey folks, I wanted to get a feel for how devs would feel about back >> porting the recent jetty and spring upgrades to the 2.8.x branch? I’ve been >> working with them on master without any issues, not sure if anyone else has >> run into any hitches though. >> >> If people do think this is a safe back port is now (with a 2.8 release >> pretty fresh out the door) a good time? >> >> Thanks! >> >> -Justin >> >> >> ------------------------------------------------------------------------------ >> Go from Idea to Many App Stores Faster with Intel(R) XDK >> Give your users amazing mobile app experiences with Intel(R) XDK. >> Use one codebase in this all-in-one HTML5 development environment. >> Design, debug & build mobile apps & 2D/3D high-impact games for multiple >> OSs. >> http://pubads.g.doubleclick.net/gampad/clk?id=254741551&iu=/4140 >> _______________________________________________ >> Geoserver-devel mailing list >> Geoserver-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/geoserver-devel >> >> > > > -- > == > GeoServer Professional Services from the experts! Visit > http://goo.gl/it488V for more information. > == > > Ing. Andrea Aime > @geowolf > 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 339 8844549 > > 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. > > ------------------------------------------------------- >
------------------------------------------------------------------------------
_______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
