Re: [Geoserver-devel] Freeze for 2.9

update: > Q: Kevin how close is geowebcache to being ready? You were looking at > upgrading security component ... > Talked to Kevin, update to spring security is slow going - but still going. -- Transform Data into Oppor

Re: [Geoserver-devel] Freeze for 2.9

Looking at geofence: 3.1.1.RELEASE 3.1.0.RELEASE There are lots of other dependencies to sync up (servlet, jettison, asm, ). -- Jody Garnett On 16 March 2016 at 14:54, Jody Garnett wrote: > Thanks to everyone for contributing to the email discus

Re: [Geoserver-devel] Freeze for 2.9

Hi Jody, so what's the revised plan? Cheers Andrea On Mon, Mar 14, 2016 at 5:00 PM, Jody Garnett wrote: > Forgive my enthusiasm - I am rather stoked that the initial "getting it to > work" has only taken a week, rather than several weeks. I had thought we > would be wrestling much longer with s

Re: [Geoserver-devel] Freeze for 2.9

I managed to make a big jump in the Acegi to Spring Security update shortly after talking to Jody.  It now seems to be working. There were a bunch of things in the old setup that seemed to be just boilerplate that SpringSecurity now does automatically, and some things that seemed not to be used a

Re: [Geoserver-devel] Freeze for 2.9

Thanks to everyone for contributing to the email discussion (not sure if I have the wiki up to date). I have two questions: Q: Kevin how close is geowebcache to being ready? You were looking at upgrading security component ... Q: Doe

Re: [Geoserver-devel] Freeze for 2.9

Forgive my enthusiasm - I am rather stoked that the initial "getting it to work" has only taken a week, rather than several weeks. I had thought we would be wrestling much longer with secruity and security-cas ... Updating the wiki now with test plan (emphasis rest-api, security, security ldap, se

Re: [Geoserver-devel] Freeze for 2.9

Sounds good. And to be clear I wasn’t advocating for a freeze or non-freeze, just asking the question so that I don’t commit something by mistake. On Mon, Mar 14, 2016 at 9:24 AM Jody Garnett wrote: > Looks like it is a non-issue, the vast majority of the spring4 migration > is done (thanks Just

Re: [Geoserver-devel] Freeze for 2.9

On Mon, Mar 14, 2016 at 4:22 PM, Jody Garnett wrote: > Looks like it is a non-issue, the vast majority of the spring4 migration > is done (thanks Justin, Kevin and Christian) and we now have testing to do. > > If I get the word from Justin I will make a beta2 this week, and we can > get back on t

Re: [Geoserver-devel] Freeze for 2.9

Looks like it is a non-issue, the vast majority of the spring4 migration is done (thanks Justin, Kevin and Christian) and we now have testing to do. If I get the word from Justin I will make a beta2 this week, and we can get back on the release train ... looking something like: - 17 March 2.9-bet

Re: [Geoserver-devel] Freeze for 2.9

Ciao Justin, for 2.9 we are already piling up the upgrade to wicket (which is causing problems, see latest emails) with the upgrade to spring 2.4 which came in at the very last minute. I guess we have allowed enough major changes wrt adding even more. All the people I talk to demand more stability

Re: [Geoserver-devel] Freeze for 2.9

I know I don’t get a vote since I am no longer PSC but as somone who contributes more than just bug fixes to the code base would this mean there would no longer be a branch open for new features until 2.9 branches off? On Mon, Mar 14, 2016 at 5:54 AM Simone Giannecchini < simone.giannecch...@geo-s

[Geoserver-devel] Freeze for 2.9

Dear All, I have talked to Andrea about whether or not we should unfreeze 2.9 given the delay for the upgrade to spring 4. From the perspective of someone who follows clients deployments, I am against unfreezing 2.9. With the delay for 2.9 we are making room for a change which is major (at least i