Yes .. please vote for this release as the application management bundle
is the last SNAPSHOT dependency that keeps us from releasing the Karaf 3
Release Candidate.
Christian
Am 20.08.2012 11:29, schrieb Holly Cummins:
Any more votes on this? We're short two pmc votes ... :)
On Wed, Aug 15, 2012 at 11:33 AM, Holly Cummins <
[email protected]> wrote:
I've staged a release candidate for the application uber-bundle and a few
left-over blueprint bundles. I am hoping this release gets the last few
bits out the door which enable the release of Karaf 3.0.0.
WHAT'S BEEN RELEASED?
The modules are staged and tagged as follows:
application-management:
https://svn.apache.org/repos/asf/aries/tags/org.apache.aries.application.management-1.0.0
application-bundle:
https://svn.apache.org/repos/asf/aries/tags/org.apache.aries.application-1.0.0
blueprint-testbundleb:
https://svn.apache.org/repos/asf/aries/tags/org.apache.aries.blueprint.testbundleb-1.0.0
blueprint-compatibility:
https://svn.apache.org/repos/asf/aries/tags/org.apache.aries.blueprint.compatibility-1.0.0
VERIFYING THE RELEASE
Instructions for verifying the release are at
http://aries.apache.org/development/verifyingrelease.html.
Alternately, cut and paste the following to run a full check (there are
two repositories, and the order matters):
wget --no-check-certificate
https://svn.apache.org/repos/asf/aries/scripts/verify_staged_release.sh
chmod a+x verify_staged_release.sh
./verify_staged_release.sh 009 mytempdirectory 2>&1 | tee
verifyresults09.txt
grep FAIL verifyresults09.txt
grep ERROR verifyresults09.txt
./verify_staged_release.sh 011 mytempdirectory 2>&1 | tee
verifyresults11.txt
grep FAIL verifyresults11.txt
grep ERROR verifyresults11.txt
SOURCE ZIPS
Artifacts are in two staged repos,
https://repository.apache.org/content/repositories/orgapachearies-009/<https://repository.apache.org/content/repositories/orgapachearies-108/>
.
If building from the source, the first repo should be built first.
Links to the *.zip files for each module are provided below:
org.apache.aries.application.management-1.0.0-source-release.zip<https://repository.apache.org/content/repositories/orgapachearies-009/org/apache/aries/application/org.apache.aries.application.management/1.0.0/org.apache.aries.application.management-1.0.0-source-release.zip>
org.apache.aries.application-1.0.0-source-release.zip<https://repository.apache.org/content/repositories/orgapachearies-011/org/apache/aries/application/org.apache.aries.application/1.0.0/org.apache.aries.application-1.0.0-source-release.zip>
org.apache.aries.blueprint.testbundleb-1.0.0-source-release.zip<https://repository.apache.org/content/repositories/orgapachearies-011/org/apache/aries/blueprint/org.apache.aries.blueprint.testbundleb/1.0.0/org.apache.aries.blueprint.testbundleb-1.0.0-source-release.zip>
org.apache.aries.blueprint.compatibility-1.0.0-source-release.zip<https://repository.apache.org/content/repositories/orgapachearies-011/org/apache/aries/blueprint/org.apache.aries.blueprint.compatibility/1.0.0/org.apache.aries.blueprint.compatibility-1.0.0-source-release.zip>
The RAT and IANAL build checks mostly passed. Note that, although RAT is
configured to ignore *.MF and other files that do not require the ASF
licence, theses files are still reported incorrectly as RAT failures. As
before, archetype-catalog.xml files fail the SHA checks but probably
shouldn't be checked. There are also some RAT warnings for
schema.map files in one the test bundle which I think can safely be
ignored.
The vote will be open for 72 hours, closing Friday lunchtime.
[ ] +1
[ ] 0
[ ] -1
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
Talend Application Integration Division http://www.talend.com
