Hi Andrea,
We intend to follow Semantic Versioning as best as possible. As
such, the 1.2.1 artifacts contain a number of bug fixes, and any
additions, while valuable, are not particularly significant. Per
the LT Handbook (1), "Service releases include bug fixes
only and include no significant new functionality."
Since we are trying to precise with language, I will acknowledge
that GeoMesa 1.2.1 is a service release.
In terms of Eclipse process, the high-level goal is to ensure that
the artifacts which a LocationTech project produces are
business-friendly and IP clean. We have completed that in its
entirety for the 1.2.0 release. Between 1.2.0 and 1.2.1, the code
contributions have been from GeoMesa committers and any changes in
dependencies have been filled appropriately and are basically
version updates for previously updated projects.
In terms of missing steps, I'm trying to figure out what we
missed... The LT handbook further states: "Release reviews are not
required for bug-fix/service releases." At the minute, we are
behind on working through Eclipse's jar signing service and
publishing to LT's download server. Perhaps some of those details
would be better for a discussion on the LT PMC or IWG email lists
since other projects will be interested in the details of cutting
service/bug-fix releases in the LT eco-system.
Cheers,
Jim
1.
https://www.eclipse.org/projects/handbook/locationtech.html#release
On 03/27/2016 06:11 PM, Andrea Ross
wrote:
Dear
Jim,
Congrats to you and the team on version 1.2.1!
This may seem like a minor point, but it's quite important. If you
would, please refrain from calling software made available outside
of the official release process a release. To do so confuses &
dilutes the value of official releases. Feel free to call it a
milestone, checkpoint, integration build, or just about any
roughly synonymous term, except release.
Also, we'd really like to see GeoMesa 1.2.0 (the official release)
up on the official download site so we can track the downloads.
That'll help us keep a close eye on the trend over time to see
growth, what works and what doesn't promoting the releases.
Cheers,
Andrea
On 25/03/16 16:58, Jim Hughes wrote:
Hi all,
I'm pleased to announce the GeoMesa 1.2.1 release. Artifacts
are available from LocationTech's Nexus repo. The changelog is
here:
https://geomesa.atlassian.net/secure/ReleaseNote.jspa?projectId=10000&version=11900.
The documentation at http://www.geomesa.org/documentation/ has
been updated.
Of note, among the bug fixes (like improving support for
non-point geometries in heatmap generation and fixing DWITHIN
again), there are few new features worth calling out:
Accumulo:
GEOMESA-1107 Adds support for S3A ingest (to the existing S3
support).
GEOMESA-960/1011 allows for pushing statistics calculations down
to the tablet servers. In particular, there's now a little DSL
for generating multiple histograms with one WPS call.
Kafka:
GEOMESA-1110 Implements the GeoTools Feature Event Listener API
for the Kafka Data Store. Tutorial/example code is available
(1).
GEOMESA-1130 Allows a consumer to specify a filter to limit
features added to the in-memory map.
For Kafka, a new load tester example is here (2).
Cheers,
Jim
1.
https://github.com/geomesa/geomesa-tutorials/blob/1.2.1/geomesa-quickstart-kafka/src/main/java/com/example/geomesa/kafka/KafkaListener.java
2.
https://github.com/geomesa/geomesa-tutorials/blob/1.2.1/geomesa-quickstart-kafka/src/main/java/com/example/geomesa/kafka/KafkaLoadTester.java
_______________________________________________
geomesa-users mailing list
geomesa-users@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://www.locationtech.org/mailman/listinfo/geomesa-users
_______________________________________________
geomesa-dev mailing list
geomesa-dev@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
http://locationtech.org/mailman/listinfo/geomesa-dev
|
