Ok, so this discussion, though it's lead to quite good discussions and
directions, has thrown us (OpenGeo) a fairly big curve ball. Which is
our fault, as the KML stuff we are working on is still being improved at
the last moment - we are normally more ahead of the game.
In the future I hope we can come up with a process that makes it so this
doesn't happen, with more future planning and understanding. But I'd
also like to see easier mechanisms to move quickly when needed, the time
spent on all these conversations has slowed us down considerably. They
obviously needed to happen, and we should have prepped more, but so it
goes. And right now it's still not clear how we could move forward as
quickly as we'd need to.
So right now we're probably going to back down from our really big PR
release, as time is just getting too tight to feel really good about the
release. We hope to do one in a month or so, when we get some external
sites crawled by GeoSearch, talking about how this data is now on the
GeoWeb.
But we will do some sort of release announcement, hopefully emphasizing
the KML Super Overlays. But right now we're unsure what to do about the
GeoSearch stuff. Right now it'd probably be more work to code the
appropriate extension points, since there needs to be switches in the
core KML code to activate it or not. So we could do that. Or we can
put together the GSIP in the next day or two to get it passed. Or else
get an exception to have the GSIP in place for 1.7.2, what we were
originally hoping for, but it sounds like Jody wants to require a GSIP.
Which we are happy to do now, as it's no longer going to be a focus.
So that we don't fall in to inaction, if no one says anything we will go
forth with a GSIP, which we'd need a vote finalized for by the end of
the week. If anyone is going to have objections to the GSIP do let us
know as soon as possible. Just wanted to give a heads up with where we
are at in the release process, and to see if anyone had thoughts. We'll
be aiming to announce the release on December 9, and would really like
to have it built with people on the lists testing in the next few days.
Chris
Jody Garnett wrote:
It was no shock to me that people are surprised about the sudden move to make rest and geosearch core modules. First off, i have to apologize b/c this process has been poorly managed by me. These needed to be included in 1.7.1 and I did not spend any time before hand working to get them to a "releasable" state.
The requirement to include these modules comes down from those who pay the bills... so not getting them into this release is not really an option.
I am not surprised by the direction; can I ask for a GSIP to be written (if not approved) for the 1.7.1 release? There are a couple of RnD links passed around in the IRC logs; but nothing formal we can consider for approval...
I am open to strategies on how to plan this road map. I know a lot of different people want to see a lot of different things and have different requirements. So I am not sure how to proceed in order to build a balanced and fair road map.
I find it useful to have a separation between deadlines/funded work and strategic direction. We only really get in trouble when deadlines are endangered by so much active development a release window cannot be found. I agree that Jira is not the best tool for this sort of planning.
Jody
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
--
Chris Holmes
OpenGeo - http://opengeo.org
Expert service straight from the developers.
--
Chris Holmes
OpenGeo - http://opengeo.org
Expert service straight from the developers.