Oops, sorry I misread your first email, i thought next week was testing
week but it is this week. But yeah officially calling the freeze would
be nice, perhaps at least until the new practices go through a few
iterations. I remember when I was doing releases a while back people
would get annoye
Justin Deoliveira ha scritto:
> And just to clarify when does the freeze occur?
It was meant to occur on Monday actually... :-(
That's what we said in the testing GSIP, one week before the release,
pens up, and start testing:
http://geoserver.org/display/GEOS/GSIP+42+-+Official+testing+team
Hopef
And just to clarify when does the freeze occur?
Andrea Aime wrote:
> Hi all,
> not sure if everybody has noticed, but beginning of next week we plan
> to have a release. This means we're in the testing week, when the
> testing team is supposed to hit GS nightly builds hard :-)
>
> Just a reminde
Thanks for the reminder! Am downloading it now...
--
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market pro
Ben Caradoc-Davies ha scritto:
> And mainly to remind myself, we are testing 2.0.x nightlies
> (2.0.1-SNAPSHOT) in preparation for the 2.0.1 release:
> http://gridlock.openplans.org/geoserver/2.0.x/
>
> I will be testing app-schema with a rather nasty Oracle deployment.
Thanks a ton Ben! :-)
F
And mainly to remind myself, we are testing 2.0.x nightlies
(2.0.1-SNAPSHOT) in preparation for the 2.0.1 release:
http://gridlock.openplans.org/geoserver/2.0.x/
I will be testing app-schema with a rather nasty Oracle deployment.
On 16/12/09 15:36, Andrea Aime wrote:
> Hi all,
> not sure if ever
Hi all,
not sure if everybody has noticed, but beginning of next week we plan
to have a release. This means we're in the testing week, when the
testing team is supposed to hit GS nightly builds hard :-)
Just a reminder anyways, I know very well the team is not paid.
Every bit of testing will be v
