I haven't seen any problems with the artifacts so I'm +1.
I built from the tags and ran 2 of our samples (AriesTrader and Blog) -
and both of those worked well.
I also did a rat scan and did not see anything obviously wrong.
I did notice some old README files that I hadn't deleted in AriesTrader
... but that is no reason to stop the vote.
I also have some concerns with the release process and the effects on
trunk. I hope that we can figure out some ways to make it easier for
future releases and eliminate some of the manual updates that Jeremy had
to make. If we continue to perform the release from trunk we will also
have to more clearly define the process - such as what is and is not
allowed to happen in trunk during the vote.
Joe
On 4/9/10 8:42 PM, Jeremy Hughes wrote:
I've staged a release candidate for Aries (Incubating) v0.1. The
following Aries top level modules are staged and tagged in
https://svn.apache.org/repos/asf/incubator/aries/tags/ at revision
932654. The artifacts are in two staged repos.
Modules staged at
https://repository.apache.org/content/repositories/orgapachearies-008/
are:
parent
eba-maven-plugin
testsupport
util
transaction
web
application
jmx
jpa
samples
Modules staged at
https://repository.apache.org/content/repositories/orgapachearies-010/
are:
blueprint
jndi
The RAT and IANAL bulid checks passed.
The vote will be open for 72 hours.
[ ] +1
[ ] +0
[ ] -1
Thanks,
Jeremy
--
Joe
