You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by Holly Cummins <ho...@googlemail.com> on 2012/08/15 12:33:47 UTC
[VOTE] Aries application uber-bundle and misc blueprint bundles
release candidate
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
Re: [VOTE] Aries application uber-bundle and misc blueprint bundles
release candidate
Posted by Christian Schneider <ch...@die-schneider.net>.
+1 (non binding)
Tested org.apache.aries.application.management on Apache Karaf.
Christian
Am 15.08.2012 12:33, schrieb Holly Cummins:
> 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
Re: [VOTE] Aries application uber-bundle and misc blueprint bundles
release candidate
Posted by Christian Schneider <ch...@die-schneider.net>.
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 <
> holly.k.cummins@googlemail.com> 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
Re: [VOTE] Aries application uber-bundle and misc blueprint bundles
release candidate
Posted by Holly Cummins <ho...@googlemail.com>.
Any more votes on this? We're short two pmc votes ... :)
On Wed, Aug 15, 2012 at 11:33 AM, Holly Cummins <
holly.k.cummins@googlemail.com> 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
>
Re: [VOTE] Aries application uber-bundle and misc blueprint bundles
release candidate
Posted by Andreas Pieber <an...@gmail.com>.
+1 (non binding)
Build on linux and tested on Karaf.
Kind regards,
Andreas
On Thu, Aug 16, 2012 at 2:44 PM, David Bosschaert
<da...@gmail.com> wrote:
> +1
>
> David
>
> On 15 August 2012 11:33, Holly Cummins <ho...@googlemail.com> 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
Re: [VOTE] Aries application uber-bundle and misc blueprint bundles
release candidate
Posted by David Bosschaert <da...@gmail.com>.
+1
David
On 15 August 2012 11:33, Holly Cummins <ho...@googlemail.com> 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
[RESULT] [VOTE] Aries application uber-bundle and misc blueprint
bundles release candidate
Posted by Holly Cummins <ho...@googlemail.com>.
Thanks everyone for your votes. The vote has been running
for five days or so, and has now passed.
Here are the results:
[+1] 8 There are 3 binding votes from PMC members (David Bosschaert, Dan
Kulp, and Stuart McCulloch), and 2 non-binding
(Andreas Pieber, and Christian Schneider).
[0] 0
[-1] 0
I'll promote the approved bundles to maven repositories and the Apache
download site. It will probably take about six hours for the bundles to be
mirrored from
Nexus to Maven Central. I think we now have enough of a 1.0.0 distribution
that I can update the Aries download pages and announce the release, too!
Cheers,
Holly
On Mon, Aug 20, 2012 at 9:38 PM, Stuart McCulloch <mc...@gmail.com> wrote:
> +1 (binding)
>
> I only saw one RAT warning, for the schema.map file in the test bundle -
> looking at the contents this is a trivial file, so I don't see this as a
> blocking issue
>
> --
> Cheers, Stuart
>
> On 15 August 2012 11:33, Holly Cummins <holly.k.cummins@googlemail.com
> >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
> >
>
>
>
> --
> Cheers, Stuart
>
Re: [VOTE] Aries application uber-bundle and misc blueprint bundles
release candidate
Posted by Stuart McCulloch <mc...@gmail.com>.
+1 (binding)
I only saw one RAT warning, for the schema.map file in the test bundle -
looking at the contents this is a trivial file, so I don't see this as a
blocking issue
--
Cheers, Stuart
On 15 August 2012 11:33, Holly Cummins <ho...@googlemail.com>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
>
--
Cheers, Stuart