brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aled Sage <aled.s...@gmail.com>
Subject Re: [DISCUSS][VOTE] Release Apache Brooklyn 0.9.0 [rc1]
Date Thu, 31 Mar 2016 20:01:21 GMT
Hi all,

When running our LoadTest on master (i.e. same code as 0.9.0 release 
candidate), I hit the deadlock described at [1]. I think others are 
unlikely to hit it, but given the consequences I suggest we fix it for 
the 0.9.0 release and produce another release candidate. I've fixed it 
in master [2,3]. They are simple code changes, but deserve careful review.

If we do produce another release candidate, I'd also want us to 
cherry-pick [4]. This fixes exceptions I was getting when serializing 
localhost machine locations, which would likely affect rebind (i.e. 
restarting Brooklyn).

Aled

[1] https://issues.apache.org/jira/browse/BROOKLYN-245
[2] https://github.com/apache/brooklyn-library/pull/29
[3] https://github.com/apache/brooklyn-server/pull/96
[4] https://github.com/apache/brooklyn-server/pull/97


On 31/03/2016 15:05, Richard Downer wrote:
> 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 list 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 wanted" - 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 o The Apache Software Foundation.
>
> 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
> inconsistently 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
> files are 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 need the actual release files to be tested manually to make sure
> that a mistake does not ruin the experience for users.
>
> So if you can spare an hour or more to download some of the artifacts
> and try 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.
>
> Thanks!
> Richard.
>
>
> ---------- Forwarded message ----------
> From: Richard Downer <richard@apache.org>
> Date: 31 March 2016 at 14:16
> Subject: [VOTE] Release Apache Brooklyn 0.9.0 [rc1]
> To: Brooklyn dev <dev@brooklyn.apache.org>
>
>
> This is to call for a vote for the release of Apache Brooklyn 0.9.0 [rc1].
>
> This release comprises of a source code distribution, and a corresponding
> binary distribution, RPM packages, Vagrant environment package, and
> Maven artifacts.
>
> The source and binary distributions, including signatures, digests, etc. can
> be found at:
> https://dist.apache.org/repos/dist/dev/brooklyn/apache-brooklyn-0.9.0-rc1
>
> The artifact SHA-256 checksums are as follows:
> c03938c4c7a060e8e50f435170e5033277f09c84a54d4abcf0d949c807de9363
> *apache-brooklyn-0.9.0-rc1-1.noarch.rpm
> 777663bbc4cf2d4228ea5dfdfd3e17b5aeaefc3a72ef51d6560fdffe27fc0f46
> *apache-brooklyn-0.9.0-rc1-bin.tar.gz
> 4dcaa31e68fed04217aa2b976675cd9b92db0d8f24735c033081ecd3128985d0
> *apache-brooklyn-0.9.0-rc1-bin.zip
> ef697bfe7d1f4b83964a008a2f92ee92282a1f6160904d3e7b51e571b0002422
> *apache-brooklyn-0.9.0-rc1-src.tar.gz
> 149eef62981f154c1bff7a0f41ddbbbc6f0b40c21997391f9a273db156a405ce
> *apache-brooklyn-0.9.0-rc1-src.zip
> 1b39a3c2da645a05026882c106d321e8f34fd19d8d3864baab88952538315d30
> *apache-brooklyn-0.9.0-rc1-vagrant.tar.gz
> cae31212f1293e557c4039138f95769d2c58de7478cbc3b5bf8a9d5c03dfd7a2
> *apache-brooklyn-0.9.0-rc1-vagrant.zip
>
> The Nexus staging repositories for the Maven artifacts are located at:
> https://repository.apache.org/content/repositories/orgapachebrooklyn-1014
> https://repository.apache.org/content/repositories/orgapachebrooklyn-1015
>
> All release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/richard.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/brooklyn/KEYS
>
> The artifacts were built from these Git commit IDs:
> brooklyn: acc8ff1930d243d2a5fae1ad2f1a1ef17ca4a19c
> brooklyn-client: 64573c8e1b8630f59b23356520282c91cc46a8a1
> brooklyn-dist: 0b8b81df458fa4323939582d9f0dda10b2f6eaee
> brooklyn-docs: 12430d193e1891b87a677d6b45a3b17861c83518
> brooklyn-library: 76c0c720edfcd9ad4f7bd70352ece6f08fb5aaad
> brooklyn-server: 1ccdef868ae798add88f51e269df87c01bd8544f
> brooklyn-ui: 307382128951bb237bc351ac22136745e5d50475
> All of the above have been tagged as "apache-brooklyn-0.9.0-rc1".
>
>
> Please vote on releasing this package as Apache Brooklyn 0.9.0.
>
> The vote will be open for at least 72 hours.
> [ ] +1 Release this package as Apache Brooklyn 0.9.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because ...
>
>
> Thanks,
> Richard.


Mime
View raw message