Doh sorry, as usual my auto-complete for geoserver completes the
"geoserver" address with "geoserver users"
(and I don't double check)
Cheers
Andrea
---------- Forwarded message ----------
From: Andrea Aime <andrea.aime@anonymised.com>
Date: Mon, May 14, 2012 at 4:25 PM
Subject: Meeting minutes for May 14 2012 meeting
To: Geotools-Devel list <geotools-devel@lists.sourceforge.net>,
GeoServer Mailing List List <geoserver-users@lists.sourceforge.net>
Hi all,
here are the meeting logs for today's meeting. Special thanks to Jody
for driving the meeting and
taking most of the notes while everybody else was talking :-p
Next meeting is in two weeks, May 28, same time, we will post a mail
on May 11 asking people
for agenda items.
Cheers
Andrea
-------------------------------
Attendees:
Justin Deoliveira, Andrea Aime, Jody Garnet (chair), Simone
Gianecchini, Alessio Fabiani, Ben Caradoc-Davies, David Winslow
May 14, 2012
AGENDA:
1) Meeting organisation
2) GeoServer / GeoTools / uDig Release Planning
Action:
- Jody to releaes 8.0-RC1 to maven and wait for ...
- Justin to release GeoServer 2.2-Beta2
- Andrea will port 2.1 release and provide helpful feedback
4) OSGeo Incubation
Action:
- Justin will look at disable the broken tests, and we need to report
issues to the CITE team
- Justin will report issue for current cite test issue that fails post
postgres 8.3
5) Time Boxed Release
Action:
- Andrea: revist next meeting then we can write
MINUTES:
Meeting Organisation
Ideas:
- Skype Worked
- Options for sharing desktop: WebEx limitations on linux (so no go),
or Google Plus (requires google plus, limit of 10)
Q: Open for Everyone?
Initially for PSC members to get their act together; but feel free to
gate crash.
OGC precident: Voting members / observers.
Q: How to join? (if you are not a PSC member)
Add yourself and you to adgenda to get an invite; organise on IRC, or
email the chair your skype details.
Q: Post the logs somewhere?
Post to mailing listing (geoserver-devel, geotools-devel).
Q: Where are we going to set the adgenda?
Email: Send email reminder, and invite people to reply with adgenda items. **
Etherpad: easy to vandlize?
Wiki: Requires sign on.
Google Docs: also an option.
GeoServer / GeoTools / uDig Release Planning
Q: Are we in a good spot to release?
jdeolive: Think so; reviewing possible blockers.
ben: reviewing blocker on wfs paging.
Q: Relase candiate?
GT release candidate, GS beta2
Expect a second beta in about four weeks (around June 18) (Ben working
through above blocker on wfs paging, and an app schema issue
[Victor]).
Q: GeoServer release tasks
- Relaese scripts: secondary priority of justin's release process.
- GEOS-5019 not a blocker for 2.2-beta2
Q: Release status?
GeoServer:
- 2.2 Beta 2 Justin is on it this week
GeoTools:
- 8.0-RC1: ready and willing
uDig 1.3.2:
- Release pening google summer of code student training; and GeoTools 8.0-RC1
CITE tests
Problem:
- WFS 1.1 Cite Tets are not written with WFS 2.0 in mind. This is
pretty unsolvable as the tests are wrong.
Solutions:
- Distable this tests that are wrong
- Andrea had an idea about returning an error
- Option to limit a workspace to only enable WFS 1.1
Action:
- Justin will look at disable the broken tests, and we need to report
issues to the CITE team
- move on with the idea about disabling the versions and fix
negotiation code collaborating over Jira
Q: Enable the CITE builds on build box?
- Yep; expect it to be broken for a couple days.
Q: GEOT-XXX Filter test which rounds down for Integer? (and like on dates too)
How to solve? Address in spare time as a higher priority thing
OSGeo Incubation
OSGeo Incubation committee has found volunteer mentor, waiting for him
to contact us on geoserver-devel.
Time boxed releases
What we are talking about:
- 1-4 months active development
- 1-2 months cool down, bug, fix, QA, release
Jody: problem is not release model, it's buy in.
Andrea: Make it cheaper in terms of time commitment - automation, tag
a working nightly build etc. Look at limiting the amount of
permissions needed get a release of done.
Ben: Back to bi-annual release model. Lots of benifit in terms of not
having to handwave with respect oranisations adopting geoserver.
Pros:
- Ben: predictability for customers
- Andrea: help with feature planning, consequences of missing a
release not as severe
- Jody: schedule of resources
Cons:
- release crunch - if any blockers show up we need a power hitter to
knock them over
Q: How to resource the predicable?
- write down what we intend
- shop it around to our participating oranisations, revise as needed
- move it over into change contorl (GSIP, RFC)
Q: Automation vs Manual
- automation - risk turning it into a justin only release if scripts fail
- andrea - needs automation to make the release "cheap" enought for
consulting oranisations to take part
Automation:
- automate: tags and builds and so on
- manual: follow up with manual script for QA
- automate: installers, upload, sourceforge (ref:
http://sourceforge.net/apps/trac/sourceforge/wiki/File%20management%20service
and http://sourceforge.net/apps/trac/sourceforge/wiki/SSH%20keys )
- note well: these scripts (bash) will run on the build box through hudson
Q: Automated uploads?
- research topic, geoserver account on source forge
- alternative to source forge? codehaus. But yeah not as good as
source forge, missing geographically distributed set of mirrors
Q: Build box for github / udig use?
- http://jenkinshosting.com/
- http://travis-ci.org/
--
Ing. Andrea Aime
GeoSolutions S.A.S.
Tech lead
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 962313
mob: +39 339 8844549
http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.youtube.com/user/GeoSolutionsIT
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf
--
Ing. Andrea Aime
GeoSolutions S.A.S.
Tech lead
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 962313
mob: +39 339 8844549
http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.youtube.com/user/GeoSolutionsIT
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf