OSDir


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [VOTE] Apache Beam, version 2.6.0, release candidate #1


Just wanted to highlight again to folks who are interested to help with qualifying the release: release validation checklist  has 2.6.0 tab that shows what has been tested so far for this RC. 

Please sign up and add your results. It may be helpful to include in the spreadsheet which operation system was used to test the SDK.

Some helpful links: 

https://beam.apache.org/contribute/release-guide/#run-validation-tests  - these are instructions how to perform release validation steps.
https://beam.apache.org/get-started/ - these are instructions Beam users may actually be following when trying out Beam.
https://s.apache.org/beam-release-validation - Validation checklist/acceptance criteria.  

Also it looks like these links may need to be updated to better reflect required action items to cover SQL and Go SDK.

thanks,
Valentyn


On Thu, Aug 2, 2018 at 10:07 PM Suneel Marthi <smarthi@xxxxxxxxxx> wrote:
+1 non-binding

1. tested with beam samples
2. verified sigs and hashes of artifacts


On Fri, Aug 3, 2018 at 12:43 AM, Jean-Baptiste Onofré <jb@xxxxxxxxxxxx> wrote:
+1 (binding)

Tested with beam-samples.

I didn't have time to include three Jira, but 2.7.0 should be in vote in
soon ;)

Regards
JB

On 01/08/2018 01:50, Pablo Estrada wrote:
> Hello everyone!
>
> I have been able to prepare a release candidate for Beam 2.6.0. : D
>
> Please review and vote on the release candidate #1 for the version
> 2.6.0, as follows:
>
> [ ] +1, Approve the release
> [ ] -1, Do not approve the release (please provide specific comments)
>
> The complete staged set of artifacts is available for your review, which
> includes:
> * JIRA release notes [1],
> * the official Apache source release to be deployed to dist.apache.org
> <http://dist.apache.org> [2], which is signed with the key with
> fingerprint 2F1FEDCDF6DD7990422F482F65224E0292DD8A51 [3],
> * all artifacts to be deployed to the Maven Central Repository [4],
> * source code tag "v2.6.0-RC1" [5],
> * website pull request listing the release and publishing the API
> reference manual [6].
> * Python artifacts are deployed along with the source release to the
> dist.apache.org <http://dist.apache.org> [2].
--
Jean-Baptiste Onofré
jbonofre@xxxxxxxxxx
http://blog.nanthrax.net
Talend - http://www.talend.com