[Geoserver-devel] cross project roadmap

jive · February 14, 2007, 11:40pm

Hi list;

Afraid I missed the GeoServer meeting yesterday - I was wanting to show up and talk about the attached picture.

These pictures show the current state of play - as I understand it. Especially with respect to GeoServer I am probably *wrong*. So please help me fill in the details, I will try and fill in the blanks.

So far I have the following blanks:
- Summer: GeoAPI 2.1.RC0 and report to working group
- March: GeoTools ISO Feature unsupported module
- March: GeoServer (branch or module?) community schema service

If you are doing work with deadlines (and you want to see it on the roadmap) reply to this email and let me know.

These pictures will eventually live here:
- http://docs.codehaus.org/display/GEOTOOLS/GTSteering+2007+Q1

(You can edit the svg attachment on that page with inkscape if you want
to help out directly)

Cheers,
Jody

(attachments)

Rob_Atkinson · February 15, 2007, 1:07am

Jody Garnett wrote:

Hi list;

Afraid I missed the GeoServer meeting yesterday - I was wanting to show up and talk about the attached picture.

These pictures show the current state of play - as I understand it. Especially with respect to GeoServer I am probably *wrong*. So please help me fill in the details, I will try and fill in the blanks.

the symbology is a little obscure - my interpreation is this:

horizontal alignment = dependency on release activities

Package(trunk) - means that the package is currently at trunk (obviously geoserver 1.6 will depend on a release of gt 2.4 off gt trunk )

colours - not sure of mapping from activity level to palette

So far I have the following blanks:

- March: GeoTools ISO Feature unsupported module
- March: GeoServer (branch or module?) community schema service

These two are going into geotools trunk as unsupported modules now, if these can be proved to work with Geoserver 1.6 then they can be released in conjunction with GS 1.6 (which only bundles supported plug-ins I guess?) - i.e. there is a process to add an unsupported module the community is going to be relatively happy with - since it will apply to many data stores. So when 1.6 goes out it would be our aim to be able to use these unsupported modules.

If you are doing work with deadlines (and you want to see it on the roadmap) reply to this email and let me know.

These pictures will eventually live here:
- http://docs.codehaus.org/display/GEOTOOLS/GTSteering+2007+Q1

(You can edit the svg attachment on that page with inkscape if you want
to help out directly)

Cheers,
Jody

------------------------------------------------------------------------

------------------------------------------------------------------------

------------------------------------------------------------------------

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
------------------------------------------------------------------------

_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

jive · February 15, 2007, 1:15am

Rob Atkinson wrote:

Jody Garnett wrote:

Hi list;

Afraid I missed the GeoServer meeting yesterday - I was wanting to show up and talk about the attached picture.

These pictures show the current state of play - as I understand it. Especially with respect to GeoServer I am probably *wrong*. So please help me fill in the details, I will try and fill in the blanks.

the symbology is a little obscure - my interpreation is this:

horizontal alignment = dependency on release activities

Got it - so reading across you can tell what version of GeoAPI / GeoTools and GeoServer line up.

Package(trunk) - means that the package is currently at trunk (obviously geoserver 1.6 will depend on a release of gt 2.4 off gt trunk )

(trunk) and (stable) indicate what the project is doing formally. (active) I just made up to show that the branch was actively working on something (in the case of geoserver 1.5 we are working towards a release).

colours - not sure of mapping from activity level to palette

The darker the color the more activity; you can see that the majority of uDig work is happening in the community plug-in space, a bit of working happening on uDig 1.1 and very little work happening on uDig 1.2 (ie trunk).

Cheers,
jody