It's a solid +1 to me.
Here is the summary of my tests:
1. downloaded all artifacts
2. verified all signatures
3. build source with tests
4. launched Brooklyn vagrant and did sanity checks, i.e. up and running
5. launched Brooklyn (zip) and did sanity checks, i.e. up and running
6. used CLI to add locations
7. deployed the 4th quick launch template (Resilient Load-Balanced Bash Web Cluster (Brooklyn Example) in AWS and verify it was working
Item 1, 2, 3 and 4 were done automatically with the attached script.
This thread is for discussions related to the release vote.
I should clarify what we are looking for in a release vote. Particularly,
we are looking for people to download,validate, and test the release.
Only if you are satisfied that the artifacts are correct and the quality is
high enough, should you make a "+1" vote. Alongside your vote you should
the checks that you made.
Here is a good example: http://markmail.org/message/gevsz2pdciraw6jw
The vote is not simply about "the master branch contains the features I
it is about making sure that *these* artifacts are *correct* (e.g. they are
not corrupted, hashes and signatures pass) and are of *sufficiently high
quality* to be stamped as an official release of The Apache Software
Why test the artifacts when master is looking good? Here are some reasons:
- somebody could have made a commit that broke it, since you last git pulled
- the release branch could have been made at the wrong point, or
between all of the submodules
- something in the release process could have broken it
- I could have made a mistake and corrupted the files
- a problem with the Apache infrastructure could mean that the release
unobtainable or corrupted
This is why the release manager needs you to download the actual release
artifacts and try them out.
The way Apache works can be a bit arcane sometimes, but it's all done with
a reason. If the vote passes then the contents of the email and its links
become "endorsed" by The Apache Software Foundation, and the Foundation will
take on legal liability for them, forever.
And of course we want the best possible experience for our users - so we
the actual release files to be tested manually to make sure that a mistake
not ruin the experience for users.
So if you can spare an hour or more to download some of the artifacts and
them out, then it will be *very* useful! The vote lasts for three days so
there's no need to rush to get a vote in.