Well, the results for our vote for release of Apache River 2.1.2 are in:
+1 Tom Hobbs
+1 Jukka Zitting
+1 Niclas Hedhman
We have 2 Incubator PMC votes and 1 River PPMC vote.
We haven't quite achieved the numbers we needed to release Apache River
on this occasion. I think what we need is a large show of support from
everybody that watches the Apache River Dev list. There's an important
patch that has been included in the River trunk since my release
artifacts were posted. I've got a busy week ahead of me, so I can't
provide new release Artifacts just yet. But when I post the Release
artifacts to vote again, lets make some noise!
In the mean time, if you know some people who have dropped out of view
recently let them know we need their support.
Cheers,
Peter.
Peter Firmstone wrote:
Please vote on releasing Apache River 2.1.2
The voting period is extended until Saturday the 27th of February 2010
and passes if a majority of at least three +1 River Incubator PMC
votes are cast.
The vote has been extended due to the size of this release and the
subsequent time needed for review.
A candidate for the Apache River 2.1.2 Release is available at
http://people.apache.org/~peter_firmstone/
The release candidate sources are zip / tar.gz archives of the sources
in:
http://svn.apache.org/repos/asf/incubator/river/jtsk/trunk/
The SHA1 checksums are:
apache-river-2.1.2-incubating-src.tar.gz:
3D06 58BC C42C 460C 4BCE F602 A3FB 4357 C5BA F65E
apache-river-2.1.2-incubating-src.zip:
71F8 2BE5 ADC9 AAB2 2D73 0B9D EF11 1E63 1749 3168
The binary release artifacts, also available there are SHA1 checksums:
apache-river-2.1.2-incubating-bin.tar.gz:
3CA5 299C 679D 8887 5442 ACA9 CAD2 618C 2A24 A26B
apache-river-2.1.2-incubating-bin.zip:
BBB8 3072 1C57 34BF BED5 954B 5DDF 41DD 322F 8303
Results from the river-dev VOTE, closed, the 12th of February are:
+1 Tom Hobbs
+1 Jukka Zitting
+1 Niclas Hedhman
Apache River
v2.1.2 Release Notes
Apache River is an effort undergoing incubation at The Apache Software
Foundation (ASF), sponsored by the Apache Incubator. Incubation is
required of all newly accepted projects until a further review indicates
that the infrastructure, communications, and decision making process
have stabilized in a manner consistent with other successful ASF
projects. While incubation status is not necessarily a reflection of the
completeness or stability of the code, it does indicate that the project
has yet to be fully endorsed by the ASF.
Apache River is aimed at the development and advancement of the River
technology core infrastructure. River technology is a service oriented
architecture that defines a programming model which both exploits and
extends Java technology to enable the construction of secure,
distributed systems which are adaptive to change.
Notes of Interest for this Release
This second release from the Apache River project is based on the
contributions of Sun's Jini Technology Starter Kit (Starter Kit) v2.1
and Service UI from Artima. The release focuses on merging the two
contributions together, structuring separate src and bin releases, and
amending the source and documentation naming/versioning/etc to the
Apache River project.
Some points of note:
* NOTICE file and source license headers updated
* Source and documentation updated for release name (Apache River
release) and version (v2.1.2)
* Graphical installer (which was a 3rd party application in the
Starter Kit) is no longer available
* The combined source and binary release in the Starter Kit has been
separated into two releases: src and bin
* The logstore implementation of com.sun.jini.outrigger.Store has
been removed
The persistent version of Outrigger relies on a pluggable
persistence layer, |com.sun.jini.outrigger.Store|. Previous
releases of the Starter Kit included two implementations of the
Store interface, /logstore/ and /snaplogstore/. This release
removes logstore.
Logstore has been around in various forms since the 1.0 version of
Outrigger. Snapstore was introduced in v2.1 of the Starter Kit.
The v2.0.n releases of the Starter Kit used logstore as the
default Store implementation, this release has no default Store.
In order to switch an existing set of configuration files,
security policy files, etc., from using logstore to snaplogstore,
you will need to change the |com.sun.jini.outrigger.store|
configuration entry (or add a store configuration entry if you
don't already have one) to yield a
|com.sun.jini.outrigger.snaplogstore.LogStore| object. You will
also need to ensure that |outrigger-snaplogstore.jar| has been
granted sufficient permissions (see Outrigger's package
documentation for a sample security
