[Geoserver-devel] Reduced Accuracy TIME

GeoServer GeoServer Developer
1

Ticket for reference: https://jira.codehaus.org/browse/GEOS-5280

I thought I had this ready in time for last week’s RC, but it introduced some build failures so I reverted it while I fixed the problems. Now the RC has also been delayed - any objections to including the TIME changes? If so I suppose the fall-back plan is to introduce the TIME parsing changes only on the master branch.

–
David Winslow
OpenGeo - http://opengeo.org/

2

On Mon, Aug 27, 2012 at 8:26 PM, David Winslow <dwinslow@anonymised.com> wrote:

Ticket for reference: https://jira.codehaus.org/browse/GEOS-5280

I thought I had this ready in time for last week’s RC, but it introduced some build failures so I reverted it while I fixed the problems. Now the RC has also been delayed - any objections to including the TIME changes? If so I suppose the fall-back plan is to introduce the TIME parsing changes only on the master branch.

Generally speaking I’m -1 on introducing new core features at RC3, the proposal we voted
about time boxed releases also states no new core features in RC state.

Can it be committed on master, and then backported later? That’s what the above proposal
says it should be handled

Cheers
Andrea

–

==
Our support, Your Success! Visit http://opensdi.geo-solutions.it for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 962313
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

3

Yes, committing on master and backporting later works fine for this.

–
David Winslow
OpenGeo - http://opengeo.org/

On Mon, Aug 27, 2012 at 2:42 PM, Andrea Aime <andrea.aime@anonymised.com> wrote:

On Mon, Aug 27, 2012 at 8:26 PM, David Winslow <dwinslow@anonymised.com> wrote:

Ticket for reference: https://jira.codehaus.org/browse/GEOS-5280

I thought I had this ready in time for last week’s RC, but it introduced some build failures so I reverted it while I fixed the problems. Now the RC has also been delayed - any objections to including the TIME changes? If so I suppose the fall-back plan is to introduce the TIME parsing changes only on the master branch.

Generally speaking I’m -1 on introducing new core features at RC3, the proposal we voted
about time boxed releases also states no new core features in RC state.

Can it be committed on master, and then backported later? That’s what the above proposal
says it should be handled

Cheers
Andrea

–

==
Our support, Your Success! Visit http://opensdi.geo-solutions.it for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 962313
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it