[Geoserver-devel] Wrapping up GeoServer 2.0 beta1 tomorrow

GeoServer GeoServer Developer
,
1

Hi all,
tomorrow I'll be wrapping up GeoServer 2.0 beta1 so that
we can release it on Monday 25 as foreseen by the
road-map.

I believe that the only other people working on trunk
are the app-schema people, but they did not provide
any feedback on the roadmap updates (if you have any
that would be appreciated).

Today I'll be wrapping up the last bug fixes and
start running cite WFS 1.1 which I know has issues
with Postgis-NG that I would like to fix.

Well, if there is any objection, let me know
Cheers
Andrea

--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.

2

Hi Andrea,
sounds good.

I should be already helping out with UI fixes but discovered a bug in ArcSDE gce that I'm finishing fixing now. So I should be able of getting to some UI fixes at most an hour from now. Do you think I can do that or the timing is too stretch?

Gabriel

Andrea Aime wrote:

Hi all,
tomorrow I'll be wrapping up GeoServer 2.0 beta1 so that
we can release it on Monday 25 as foreseen by the
road-map.

I believe that the only other people working on trunk
are the app-schema people, but they did not provide
any feedback on the roadmap updates (if you have any
that would be appreciated).

Today I'll be wrapping up the last bug fixes and
start running cite WFS 1.1 which I know has issues
with Postgis-NG that I would like to fix.

Well, if there is any objection, let me know
Cheers
Andrea

--
Gabriel Roldan
OpenGeo - http://opengeo.org
Expert service straight from the developers.

3

Gabriel Roldan ha scritto:

Hi Andrea,
sounds good.

I should be already helping out with UI fixes but discovered a bug in ArcSDE gce that I'm finishing fixing now. So I should be able of getting to some UI fixes at most an hour from now. Do you think I can do that or the timing is too stretch?

I'll be packaging the release tomorrow afternoon anyways so no problem.
Only, we're very close to the release so be extra careful with the
changes you're making

Cheers
Andrea

--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.

4

Andrea Aime wrote:

Gabriel Roldan ha scritto:

Hi Andrea,
sounds good.

I should be already helping out with UI fixes but discovered a bug in ArcSDE gce that I'm finishing fixing now. So I should be able of getting to some UI fixes at most an hour from now. Do you think I can do that or the timing is too stretch?

I'll be packaging the release tomorrow afternoon anyways so no problem.

cool

Only, we're very close to the release so be extra careful with the
changes you're making

sure. Nothing that cannot be told to be just a "fix" :slight_smile:

Cheers
Andrea

--
Gabriel Roldan
OpenGeo - http://opengeo.org
Expert service straight from the developers.

5

The app-schema stuff is working to a degree (a few data types not
encoding correctly and filters barfing) without special modification
to the main Geoserver codebase.

Current issues seems to be centered around a few incomplete
implementations in GML objects, requiring some patches to geotools.
Its not quite feature-complete, but may be in a week or so.

IMHO it would be good to include these app-schema elements (initially
build with the -Papp-schema profile) in the beta so that we are
getting maximum testing early that the app-schema stuff doesnt
actually interfere with anything. If problems do arise, that seem to
be hard to resolve, you can always back it out in a second cut.

The unit tests for app-schema could be disabled if the build time is
an issue, since this beta is not about testing the app-schema
functionality yet.

Regards
Rob Atkinson

On Fri, May 22, 2009 at 1:22 AM, Gabriel Roldan <groldan@anonymised.com> wrote:

Andrea Aime wrote:

Gabriel Roldan ha scritto:

Hi Andrea,
sounds good.

I should be already helping out with UI fixes but discovered a bug in
ArcSDE gce that I'm finishing fixing now. So I should be able of
getting to some UI fixes at most an hour from now. Do you think I can
do that or the timing is too stretch?

I'll be packaging the release tomorrow afternoon anyways so no problem.

cool

Only, we're very close to the release so be extra careful with the
changes you're making

sure. Nothing that cannot be told to be just a "fix" :slight_smile:

Cheers
Andrea

--
Gabriel Roldan
OpenGeo - http://opengeo.org
Expert service straight from the developers.

------------------------------------------------------------------------------
Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT
is a gathering of tech-side developers & brand creativity professionals. Meet
the minds behind Google Creative Lab, Visual Complexity, Processing, &
iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian
Group, R/GA, & Big Spaceship. http://www.creativitycat.com
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

6

Rob Atkinson ha scritto:

The app-schema stuff is working to a degree (a few data types not
encoding correctly and filters barfing) without special modification
to the main Geoserver codebase.

Current issues seems to be centered around a few incomplete
implementations in GML objects, requiring some patches to geotools.
Its not quite feature-complete, but may be in a week or so.

IMHO it would be good to include these app-schema elements (initially
build with the -Papp-schema profile) in the beta so that we are
getting maximum testing early that the app-schema stuff doesnt
actually interfere with anything. If problems do arise, that seem to
be hard to resolve, you can always back it out in a second cut.

The unit tests for app-schema could be disabled if the build time is
an issue, since this beta is not about testing the app-schema
functionality yet.

Rob,
isn't it a little late for inclusion in beta1?
I have no idea of what is needed to test it out (I know I asked Ben
about that, but then due to pressure in other directions I passed
the ball to Gabriel), and as you say you still have
rough edges functionality wise.

Afaik there is no public tutorial in the documentation, there is
no UI, so even in the hypothesis that I include the application
schema work in the build, how should I word the announcement?
"And oh, we have this great complex feature and app schema mapping
  support, here is a sample data directory, good luck finding the
files that do configure complex features among the rest, which
is btw not documented since you're not supposed to mess with it".

Jokes aside, in a release announcement I need a somewhat user
presentable story and a simple tutorial that works. Today I'll be fixing
the last jira issues and run all the CITE tests, so I won't have
time to figure out how mapping works and make and example
and a tutorial based on top of it.

However, if you have been following the "road map update"
mails you should know there will be a beta2 June 15
(http://geoserver.org/display/GEOS/Roadmap) so you should
have time to fix the rough edges, make a little
tutorial and provide us some hints of what is needed to
include app schema support in a release.

We have been asking updates from the app schema crowd in
the last "roadmap update" mail and we got nothing
back, so I don't feel like delaying the first
beta because of this. Others may disagree, feedback welcomed
(yes PSC members, I'm looking at you)

http://www.nabble.com/road-map-update%2C-May-12%2C-09-td23509366.html#a23509366

Let me know
Cheers
Andrea

--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.

7

We have been asking updates from the app schema crowd in
the last "roadmap update" mail and we got nothing
back, so I don't feel like delaying the first
beta because of this. Others may disagree, feedback welcomed
(yes PSC members, I'm looking at you)

The 15th seems close enough; I would like a roadmap update just so I
can guess what to expect out of the app-server project.

Jody

8

Andrea Aime wrote:

However, if you have been following the "road map update"
mails you should know there will be a beta2 June 15
(http://geoserver.org/display/GEOS/Roadmap) so you should
have time to fix the rough edges, make a little
tutorial and provide us some hints of what is needed to
include app schema support in a release.

For the benefit of the list, there has been a chat on the side, and AuScope will aim to get app-schema in beta2 (15 June), with a tutorial up by 8 June.

--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer, CSIRO Exploration and Mining
Australian Resources Research Centre
26 Dick Perry Ave, Kensington WA 6151, Australia

9

OK - if you are happy to include it in beta2, without having had the
advantage of testing its happy co-existence (not the functionality) as
per my suggestion, thats fine.

I was never advocating getting people to beta-test that part of the
functionality, so the rest of the issues are not relevant for beta1,
but they obviously would be for beta2 so thanks for laying it out.

Sorry about the late response to the roadmap - I only got something
running yesterday to give me confidence it would be worth aiming at
this round of betas.

R

On Fri, May 22, 2009 at 5:00 PM, Andrea Aime <aaime@anonymised.com> wrote:

Rob Atkinson ha scritto:

The app-schema stuff is working to a degree (a few data types not
encoding correctly and filters barfing) without special modification
to the main Geoserver codebase.

Current issues seems to be centered around a few incomplete
implementations in GML objects, requiring some patches to geotools.
Its not quite feature-complete, but may be in a week or so.

IMHO it would be good to include these app-schema elements (initially
build with the -Papp-schema profile) in the beta so that we are
getting maximum testing early that the app-schema stuff doesnt
actually interfere with anything. If problems do arise, that seem to
be hard to resolve, you can always back it out in a second cut.

The unit tests for app-schema could be disabled if the build time is
an issue, since this beta is not about testing the app-schema
functionality yet.

Rob,
isn't it a little late for inclusion in beta1?
I have no idea of what is needed to test it out (I know I asked Ben
about that, but then due to pressure in other directions I passed
the ball to Gabriel), and as you say you still have
rough edges functionality wise.

Afaik there is no public tutorial in the documentation, there is
no UI, so even in the hypothesis that I include the application
schema work in the build, how should I word the announcement?
"And oh, we have this great complex feature and app schema mapping
support, here is a sample data directory, good luck finding the
files that do configure complex features among the rest, which
is btw not documented since you're not supposed to mess with it".

Jokes aside, in a release announcement I need a somewhat user
presentable story and a simple tutorial that works. Today I'll be fixing
the last jira issues and run all the CITE tests, so I won't have
time to figure out how mapping works and make and example
and a tutorial based on top of it.

However, if you have been following the "road map update"
mails you should know there will be a beta2 June 15
(http://geoserver.org/display/GEOS/Roadmap) so you should
have time to fix the rough edges, make a little
tutorial and provide us some hints of what is needed to
include app schema support in a release.

We have been asking updates from the app schema crowd in
the last "roadmap update" mail and we got nothing
back, so I don't feel like delaying the first
beta because of this. Others may disagree, feedback welcomed
(yes PSC members, I'm looking at you)

http://www.nabble.com/road-map-update%2C-May-12%2C-09-td23509366.html#a23509366

Let me know
Cheers
Andrea

--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.

10

Rob Atkinson ha scritto:

OK - if you are happy to include it in beta2, without having had the
advantage of testing its happy co-existence (not the functionality) as
per my suggestion, thats fine.

I was never advocating getting people to beta-test that part of the
functionality, so the rest of the issues are not relevant for beta1,
but they obviously would be for beta2 so thanks for laying it out.

Sorry about the late response to the roadmap - I only got something
running yesterday to give me confidence it would be worth aiming at
this round of betas.

The sooner we have it setup so that all developers can test
it out, the better. That's why I suggested to have the tutorial
ready one week before the beta2 release, so that other devs can
walk through it and get a feeling of how things work (yes, we
may be able to figure it out just looking at the code and
config files, but we might not have the time to approach it
that way).

Cheers
Andrea

--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.