Re: [Geoserver-devel] GeoServer 2.11.0 release artifacts ready for testing

Jody has started a blog post for the release. I've given it a read-over and fixed up some typos. There is still some room for more content (e.g. an example of the REST API password endpoint). The "And more" section at the bottom could

Re: [Geoserver-devel] GeoServer 2.11.0 release artifacts ready for testing

No problem Andrea, it seems like the Windows build box was online at the time, so everything is fine. Torben On Wed, Mar 22, 2017 at 1:51 PM, Andrea Aime wrote: > > > Il 22 Mar 2017 21:36, "Torben Barsballe" ha > scritto: > > > I'm

Re: [Geoserver-devel] GeoServer 2.11.0 release artifacts ready for testing

Il 22 Mar 2017 21:36, "Torben Barsballe" ha scritto: I'm not quite sure what you mean here, Jody. By chat he told me "windows build box is screwed up so send an email when ready." But I did not understand that I was supposed to mail before running the job, I

Re: [Geoserver-devel] GeoServer 2.11.0 release artifacts ready for testing

I have tried out the OS X DMG build artifact, everything seems fine. We needed some warning before that release job, I get ready and rerun the > build. > I'm not quite sure what you mean here, Jody. Torben -- Check out

Re: [Geoserver-devel] GeoServer 2.11.0 release artifacts ready for testing

We needed some warning before that release job, I get ready and rerun the build. On Wed, Mar 22, 2017 at 1:03 PM Torben Barsballe < tbarsba...@boundlessgeo.com> wrote: > The windows build box is currently running (the installer job is in > progress). However, due to ongoing issues, the installer

Re: [Geoserver-devel] GeoServer 2.11.0 release artifacts ready for testing

The windows build box is currently running (the installer job is in progress). However, due to ongoing issues, the installer build will be quite slow (between 5 and 9 hours). Oddly enough, the above failure seems to be in communicating with the OS X build box, rather than the Windows build box. I

[Geoserver-devel] GeoServer 2.11.0 release artifacts ready for testing

Hi, the release job just finished and the release artifacts are ready for testing: http://ares.boundlessgeo.com/geoserver/release/2.11.0/ If I got Jody correctly, the OSX installer should show up, but the windows one won't and will have to be generated manually instead? Or something like that?

Re: [Geoserver-devel] Can we get a boundless maven repository account for Alessandro?

On it, will send details to Alessandro directly. -- Jody Garnett On 22 March 2017 at 11:35, Andrea Aime wrote: > Hi, > Alessandro cannot deploy the GWC artifacts to the boundless repo > because he does not have an account. > > Can someone generate one for him and

[Geoserver-devel] Can we get a boundless maven repository account for Alessandro?

Hi, Alessandro cannot deploy the GWC artifacts to the boundless repo because he does not have an account. Can someone generate one for him and then send it to alessandro.pa...@geo-solutions.it ? Thanks! Cheers Andrea -- == GeoServer Professional Services from the experts! Visit

Re: [Geoserver-devel] Do we need a proposal to manage/police last minute rush fixes?

For review: https://github.com/geoserver/geoserver/pull/2178 -- Jody Garnett On 22 March 2017 at 11:08, Andrea Aime wrote: > On Wed, Mar 22, 2017 at 7:05 PM, Jody Garnett > wrote: > >> How about we update

Re: [Geoserver-devel] last minute Geos/Geot fixes

Hi Andrea, Apologies for the late fixes and notification. The release doesn't need to be held up due to Geos PR 2175 or Geot PR 1518 that were submitted yesterday. We are more concerned with

Re: [Geoserver-devel] Do we need a proposal to manage/police last minute rush fixes?

On Wed, Mar 22, 2017 at 7:05 PM, Jody Garnett wrote: > How about we update http://docs.geoserver.org/latest/en/developer/ > release-guide/index.html#notify-developer-list to the following: > > Before: *It is good practice to notify the GeoServer developer list of > the

Re: [Geoserver-devel] Do we need a proposal to manage/police last minute rush fixes?

How about we update http://docs.geoserver.org/latest/en/developer/release-guide/index.html#notify-developer-list to the following: Before: *It is good practice to notify the GeoServer developer list of the intention to make the release a few days in advance, even though the release date has been

Re: [Geoserver-devel] Do we need a proposal to manage/police last minute rush fixes?

Hum... I would not limit myself to blockers only, but surely want to avoid the pull request merge deathmark and last minute run at the fixes. How about this, for any release the last 24/48 hours before the release are "frozen", the release branch sees no commits unless otherwise authorized? And

Re: [Geoserver-devel] Do we need a proposal to manage/police last minute rush fixes?

Okay, we do have sending an email/reminder out as part of our release procedure. Could we make a policy of only blockers can be merged after that time? -- Jody Garnett On 22 March 2017 at 10:19, Andrea Aime wrote: > On Wed, Mar 22, 2017 at 6:10 PM, Jody Garnett

Re: [Geoserver-devel] Do we need a proposal to manage/police last minute rush fixes?

On Wed, Mar 22, 2017 at 6:10 PM, Jody Garnett wrote: > Andrea I woud prefer to leave the release volunteer in charge here - as > they are putting in the work and have a limit to how much they can deal > with. > Ah, this criteria is really broken from another point of

Re: [Geoserver-devel] Do we need a proposal to manage/police last minute rush fixes?

On Wed, Mar 22, 2017 at 6:10 PM, Jody Garnett wrote: > Andrea I woud prefer to leave the release volunteer in charge here - as > they are putting in the work and have a limit to how much they can deal > with. > I strongly disagree, it leads to the current situation where

Re: [Geoserver-devel] Do we need a proposal to manage/police last minute rush fixes?

Andrea I woud prefer to leave the release volunteer in charge here - as they are putting in the work and have a limit to how much they can deal with. To that end I try and send out an email a week/days before each release asking for any incoming risks/fixes. -- Jody Garnett On 22 March 2017 at

[Geoserver-devel] [JIRA] (GEOS-8046) WPS ApplicationContext is unset Warnings

Title: Message Title Steve Ikeoka created

Re: [Geoserver-devel] WCS 2.0.1 with SCALESIZE [SOLVED]

Hi Andrea, What spec you are reading? All examples in OGC® Web Coverage Service Interface Standard - Scaling Extension are using the short format …& SCALEFACTOR=2.0 &… …& SCALEAXES=i(3.5),j(3.5),k(2.0) &… …& SCALESIZE=i(1000),j(1000),k(10) &… …& SCALEEXTENT=i(10:20),j(20:30) &… or as XML i

Re: [Geoserver-devel] proposed change: coverage readers custom dimension data type conversion

Hi Niels, there is one test about custom dimensions treatment that was contributed by Mike Benowitz years ago, I've cc'ed him along with another fellow at GDIT, they might be affected (or not). I also know GeoMesa has their own custom readers, no idea if they are dimension enabled or not. Cc'ed

[Geoserver-devel] proposed change: coverage readers custom dimension data type conversion

Hello, This message is particularly aimed at people who develop/use coverage readers that support custom dimensions, but are outside of the main geotools/geoserver code base. I am proposing a change that may affect them (see https://osgeo-org.atlassian.net/browse/GEOS-7989). In short: At

[Geoserver-devel] [JIRA] (GEOS-8045) ChannelSelection after raster RenderingTransformation may throw a IllegalArgumentException: Band number N is not valid

Title: Message Title Daniele Romagnoli

Re: [Geoserver-devel] Do we need a proposal to manage/police last minute rush fixes?

LOL, just saw this on twitter: https://twitter.com/nixcraft/status/844483236113764352 Cheers Andrea On Wed, Mar 22, 2017 at 9:26 AM, Andrea Aime wrote: > Hi, > and here we are again, ready to click on the 2.11.0 after announcements, a > freeze, a beta and a RC,

[Geoserver-devel] Do we need a proposal to manage/police last minute rush fixes?

Hi, and here we are again, ready to click on the 2.11.0 after announcements, a freeze, a beta and a RC, and people rushing in the day before to get more changes in. Do we need some clear procedure to avoid this mis-practice? Last minute fixes have their place for something that would just ruin

Re: [Geoserver-devel] GeoServer 2.11 release volunteer needed, and date determined

Sorrry for the delay GEOS-8030 is now fixed. -- Jody Garnett On 22 March 2017 at 00:20, Andrea Aime wrote: > Hi Jody, > I have not seen a commit of yours regarding this fix. Which weekend were > you talking about again? > > Cheers > Andrea > > On Fri, Mar 17, 2017

Re: [Geoserver-devel] WCS 2.0.1 with SCALESIZE [SOLVED]

Hi Jukka, that is actually not clear to me, the examples in the spec that I could find are all using the long format, but I could not find a specific rule for axis names, or how the labels reported in DescribeCoverage output relate to the IDs used in requests, since the former always uses short

Re: [Geoserver-devel] [GEOS-8042] fix for InsertElementHandler

Hi Morgan, the release was supposed to happen this morning but the windows service (supposedly a blocker) fix did not get in. That said, we regularly have bad experiences with last minute fixes, so either this one waits, or we'll have to delay the release a few days (at this point, do it next

Re: [Geoserver-devel] GeoServer 2.11 release volunteer needed, and date determined

Hi Jody, I have not seen a commit of yours regarding this fix. Which weekend were you talking about again? Cheers Andrea On Fri, Mar 17, 2017 at 8:01 PM, Jody Garnett wrote: > I will take on the windows server thing this weekend, if you can confirm > the release date. >