Hi Geoff, if this was a 1.0.0 final then I'd agree we wouldn't want an
embarrassing bug like this. But since it's a milestone release I'm happy
for it to be noted in the documentation / release notes.
Richard.
On Thu, 13 Sep 2018 at 23:28, Geoff Macartney
wrote:
> I do note the new issue
I do note the new issue Richard raised about the slow start, BROOKLYN-601.
I don't necessarily see this as a blocker, as it's something that can be
worked around, but I guess it would be nice to fix it, so I could probably
be persuaded to change my vote :-) . What does anyone else think?
G
On
+1 from me
Checks successfully completed:
[✓] Download links work.
[✓] Checksums and PGP signatures are valid.
[✓] Expanded source archive matches contents of RC tag.
[✓] Expanded source archive builds and passes tests.
[✓] LICENSE is present and correct.
[✓] NOTICE is present and correct,
+1 from me.
Here's what I tested:
1. installed/ran brooklyn (tar.gz) from local machine (os x); used it
to spin up a blueprint for...
2. install/run brooklyn (rpm) on CentOS machine in AWS
3. deployed each of the 4 templates to aws:
1. server-template
2. bash-web-server-template
Hi all
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
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,
