I am not sure how useful I find our one month delay since I do not know of any users downloading our nightly builds and providing feedback (and thus testing) based on them.
Aside: When sending these requests please quote the bug description as I cannot keep all our open issues straight (and thus always have to click the link).
So this one is for “Allowing customization of coverage band details on layer configuration would be a nice improvement.”
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment
Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees
On Fri, Apr 11, 2014 at 2:10 AM, Jody Garnett <jody.garnett@anonymised.com>wrote:
I am not sure how useful I find our one month delay since I do not know of
any users downloading our nightly builds and providing feedback (and thus
testing) based on them.
Yeah, it was never meant for user testing, but for devs one, you use
GeoServer to do your own development, the one
month is to make sure the new feature is not causing severe issues that
would hopefully show up in devs day to day work.
As for user testing, our user community is pretty much useless from that
point of view, bugs about 2.5.x series are starting
to be reported now, we got very little out of betas and RCs (it's not like
we did not give them time, beta + rc1 + rc2 was a two
months long period)... so I would not worry about user testing anyways
Cheers
Andrea
--
Meet us at GEO Business 2014! in London! Visit http://goo.gl/fES3aK
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
------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment
Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees
--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment
Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees
–
Ben Caradoc-Davies Ben.Caradoc-Davies@anonymised.com
Software Engineer
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre
This transmission is intended for the named addressee(s) only and may contain sensitive or protectively marked material up to RESTRICTED and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation.
···
On reflection I wonder if part of this is a consequence of the rapid regular releases that GeoServer does. Consider: when a new version of Windows or even ArcGIS is released it’s years after the last version and has tons of new stuff. Some users download the beta/RC’s to see what’s new, while departments download it to test if it’s compatible with their systems and devs to see what it’ll take to create new apps for it. Contrast with GeoServer - there are rarely any major changes between versions, and as new versions are only 6 months apart departments are unlikely to be considering upgrading straight off the bat (indeed, that’s why there was that GSIP a few months ago for more maintenance releases).
Combined with the low percentage of users who test betas/RC’s in the first place (be it Windows, ArcGIS, or GeoServer) and this seems like a logical consequence.
Disclaimer - I like the regular releases!
Cheers,
As for user testing, our user community is pretty much useless from that point of view, bugs about 2.5.x series are starting
to be reported now, we got very little out of betas and RCs (it’s not like we did not give them time, beta + rc1 + rc2 was a two
months long period)… so I would not worry about user testing anyways
