[Geoserver-devel] Jenkins build is back to normal : geoserver-master #5563

See -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _

[Geoserver-devel] Build failed in Jenkins: geoserver-master #5562

See -- [...truncated 538.58 KB...] [INFO] [INFO] Skipping GeoServer INSPIRE Extensions [INFO] This project has b

[Geoserver-devel] GWC API changes and beta release date

We have been working on the GeoWebCache Configuration API changes and REST improvements discussed here and here for the last while, in an attempt to get them in before

Re: [Geoserver-devel] Suggesting a small change in release procedures: can we cut the stable branch on beta?

First of all, the change seems reasonable, so +1 there. I have no issues with applying these changes right away for the beta release next week, and we can do a GSIP later. I'll also update the release docs while I do the release. Torben On Fri, Feb 16, 2018 at 8:30 AM, Andrea Aime wrote: > On

Re: [Geoserver-devel] GSIP 165 - Add isolated workspaces concept to GeoServer, quick vote :)

Hi all, Thanks all for the feedback and quick voting, much appreciated :) The pull requests has been reviewed and its suggestions applied: https://github.com/geoserver/geoserver/pull/2746 Cheers, Nuno Oliveira On 02/13/2018 01:40 PM, Nuno Oliveira wrote: Hi all, You may remember a few discu

Re: [Geoserver-devel] Suggesting a small change in release procedures: can we cut the stable branch on beta?

On Fri, Feb 16, 2018 at 11:44 AM, Ian Turton wrote: > I agree we hardly ever see any feedback before the .0 release. Which is a > shame but nothing we do seems to make a difference to customers. > Ah hem, "users" :-p Cheers Andrea == GeoServer Professional Services from the experts! Visit htt

Re: [Geoserver-devel] Suggesting a small change in release procedures: can we cut the stable branch on beta?

We could also cut the beta just to confirm master is releasable, and not branch. Make the first release candidate the branch to achieve the same effect. It has the advantage of less moving parts, but we do not get a code freeze to focus on bugs. But as you point out that is not happening so much.

Re: [Geoserver-devel] Suggesting a small change in release procedures: can we cut the stable branch on beta?

On Fri, Feb 16, 2018 at 4:18 AM, Ben Caradoc-Davies wrote: > +1. It does seem that we are not getting much benefit from waiting until > RC to branch, and any fix would be applied to master and the new stable > before the .0 release. We could drop the RC altogether. The current > procedure incurs

[Geoserver-devel] GeoServer Importer maximum running jobs

Dear all, I'm using the GeoServer importer and I noticed I can start as many sessions I want without receiving an error. Some of the sessions will simply go back to a "ready" state without having effect. After a little digging I foung this class: https://github.com/geoserver/geoserver/blob/master/