Andrea,
Oracle Java 8 javac fails to compile RangeCombiner.addRange because it
has started noticing that the two instances of in the parameter list
might not be the same type:
https://github.com/geotools/geotools/blob/master/modules/library/main/src/main/java/org/geotools/filter/visitor/RangeCo
On 22/12/15 02:21, Andrea Aime wrote:
> If you have doubts other have made mistakes
No, just a discussion of how to check in the context of a manual Jira
release. I am happy for a release manager to check any fixVersions I
set. I am just suggesting one way it might be done.
> So yes, the commit
On Mon, Dec 21, 2015 at 12:33 PM, Ben Caradoc-Davies
wrote:
> I see no tag for 2.7.5 in GitHub nor a call for artifact testing. Are you
> sure this issue was omitted? In the release procedure, release in Jira is
> the first step. If the steps were performed out of order and you are sure
> 2.7.5 h
PostgreSQL has a several ways to store dates that might be problematic:
- timestamp without time zone
- date without a time of day.
http://www.postgresql.org/docs/9.4/static/datatype-datetime.html
Assuming we're limiting the scope to PostgreSQL with one of these column types:
(a) +1 for removin
Hi all,
thank you very much for your response.
I did some more research on this:
Most important: I was wrong, dates can be time zoned:
http://www.w3.org/TR/xmlschema-2/#date. The XML spec for dates and times is
inspired by ISO 8601. Both, the XML spec and ISO 8601 allow the time zone
postfix "Z"
On 22/12/15 00:21, Andrea Aime wrote:
> On Mon, Dec 21, 2015 at 12:16 PM, Ben Caradoc-Davies
> wrote:
>> Looks like there is already a GS 2.7.6 version (naughty, naughty, Jira
>> makes is far too easy for an administrator to inadvertently add a
>> version); someone has an issue for it:
>> https://
On Mon, Dec 21, 2015 at 12:16 PM, Ben Caradoc-Davies
wrote:
> Looks like there is already a GS 2.7.6 version (naughty, naughty, Jira
> makes is far too easy for an administrator to inadvertently add a
> version); someone has an issue for it:
> https://osgeo-org.atlassian.net/browse/GEOS-7353
> Co
Ian,
yes, the Jira API changed when we moved from Codehaus and the Python
script is broken. Not as smooth as your last releases in 2014.
The undocumented manual procedure is to for each project:
- Manually perform the release in Administration / Versions and release
the version using the "..."
It seems that both GeoTools and GeoServer's release-jira jobs fail (and
have been failing for 9 and 6 months) - I assume this is related to the
change of jira hosting, is there a new script or manual step that I need to
run before hitting publish for the new releases?
Cheers
Ian
--
Ian Turton
