The plan I plan to plan (with the paymaster's consent) is:
1. Achieve basic WFS 1.1, GML 3.1 capabilities required, implementing test
cases.
2. Deploy to time-sensitive testbed activity
3. Port to trunk, and debug against test cases and WMS capability
4. Hopefully update deployments to include WMS functionality.
If #3 looks problematic, we may be required to fork WMS module as well.
and, we are all desperate to start working against trunk so we can do those
key bits: performance tune and improve configuration process.
Rob A
On Wed, May 21, 2008 at 12:03 PM, Ben Caradoc-Davies
<[EMAIL PROTECTED]> wrote:
> Chris Holmes wrote:
>
>> Is all the community schema work still taking place on a forked module on
>> 1.6.x?
>>
>
> Yes.
>
> It seems like a bunch of effort is being put into it there, which will
>> then all have to be ported?
>>
>
> That is correct. And it sucks. We have hard deadlines that require delivery
> now and cannot wait for a port to trunk. Yes, this is making more work for
> ourselves. Yes, I will resist all attempts to add new features until the
> port to trunk is done. In some cases, my resistance is futile.
>
> What readiness on trunk is being waited for? It has the new feature model
>> on it, and we've done an alpha release.
>>
>
> I think the trunk is satisfactory. Trunk is not the problem.
>
> Is there a plan to get on trunk? Or maybe I missed it and it's already
>> there?
>>
>
> There is a stated goal. I am not sure if it has been published. There is no
> plan, per se. I will make enquiries and report back.
>
> --
> Ben Caradoc-Davies <[EMAIL PROTECTED]>
> Software Engineer, CSIRO Exploration and Mining
> Australian Resources Research Centre
> 26 Dick Perry Ave, Kensington WA 6151, Australia
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
