Hi all,
last December Christmas got to us and we failed to release the
first beta and declare the feature freeze, which were supposed
to happen on December 21th.
All in all it was not such a bad thing, we managed to get quite
a bit new things in during January, maybe we can consider changing
the
I prefer branching at the release candidate phase, but yeah In understand if we
lock down trunk (feature freeze) today then we should create a branch to allow
RnD to continue.
Lets discuss at the meeting this evening (I would like to get CCbyA and the
headers fixed up before a branch occurs
On Mon, Jan 21, 2013 at 9:28 AM, Jody Garnett jody.garn...@gmail.comwrote:
I prefer branching at the release candidate phase, but yeah In understand
if we lock down trunk (feature freeze) today then we should create a branch
to allow RnD to continue.
Right. Not such a big deal given how git
Hi Mikel,
I'm not familiar with Raster Data nor with this plugin, but from looking at the
source code it seems likely that there is a bug in the source code.
Could other devs please look at
org.geotools.coverage.grid.io.AbstractGridCoverage2DReader.decimationOnReadingControl
and confirm or
The product archives produced okay, running them locally as a smoke test
results in the following failure:
---
Test set: org.geotools.data.wfs.v1_1_0.TinyOwsTest
GeoTools/GeoServer Meeting 2013-01-21
=
Agenda:
- GeoTools 9.0-beta1
- GeoServer 2.3-beta1
- Remaining Change Requests
- Branch for Beta?
- OSGeo Incubation
- Generated/Dynamic Layers
Participants:
Andrea Aime
Jukka Rahkonen
Ben Caradoc-Davies
Jody Garnett
Alessio
Just the Actions:
- Jody to update GSIP wiki based on above discussion.
- Ben to ask Justin about Xerces
- Andrea to round up volunteers to work on hudson (schedule new targets etc..).
Shall we drop 2.1.x
- Andrea to update data README.RST (thanks!)
- Jody to ask Justin about header (decision
On Mon, Jan 21, 2013 at 3:14 PM, Jody Garnett jody.garn...@gmail.com wrote:
Davide is this one yours? You can fix the test by referencing the
GeoTools.getVersion().
Hi,
yes. I've fixed it:
https://github.com/geotools/geotools/pull/113
==
Our support, Your Success! Visit
I agree with Christian on this one. I generally think that master should be
open for development at all times even though i am a firm believer in doing
all non trivial work on feature/topic branches until they are stable enough
to be merged into master.
Setting up the new build jobs shouldn't be
Hi Brett, Mikel,
Could other devs please look at
org.geotools.coverage.grid.io.AbstractGridCoverage2DReader.decimationOnReadingControl
and confirm or deny that there is no possibility of a rounding error,
underflow or double to int conversion that results in a negative number!
Mikel, it
Justin,
at Monday's meeting we were wondering if you have had time to progress
the removal of (external) Xerces dependencies. My understanding is that
you were pretty close. Or are you waiting until after this release cycle?
Kind regards,
Ben.
On 02/11/12 15:43, Ben Caradoc-Davies wrote:
See http://hudson.opengeo.org/hudson/job/geotools-8.x-nightly/199/
--
[...truncated 246 lines...]
[INFO] Uploading repository metadata for: 'snapshot
org.geotools.maven:jar-collector:8-SNAPSHOT'
[INFO] Retrieving previous metadata from opengeo
[INFO]
Went mostly smoothly, had to manually upload artefacts to source forge (script
problem transferring the files, I think due to the GeoTools 9 releases folder
not being created yet?
-
http://sourceforge.net/projects/geotools/files/GeoTools%209%20Releases/9.0-beta1/
I did test the build
13 matches
Mail list logo