-1.Unfortunately we discovered an issue that can cause pipelines to crash when Cythonized version of the SDK is used: https://issues.apache.org/jira/browse/BEAM-5069I think we will need another RC that has the fix. Note that we can continue validating RC1 - if there are any issues remaining, it's better if we can discover them in RC1 that in RC2.Thanks,ValentynOn Fri, Aug 3, 2018 at 1:19 AM Tim Robertson <timrobertson100@xxxxxxxxx> wrote:+1 (non binding)With apologies to Valentyn and others, but only had time to test what was feasible for us this week. Tested our existing pipelines using 2.6.0RC1 which source and sink using AvroIO / HDFS on Spark 2.3 (Cloudera) ran without issue - our project tests all pass with 2.6.0RC1.We'd like to raise that BEAM-4750 is noticeable and our project builds have slowed significantly (tests). In general we encourage effort towards (and thank those progressing) structured monitoring of performance across releases.On Fri, Aug 3, 2018 at 9:32 AM, Valentyn Tymofieiev <valentyn@xxxxxxxxxx> wrote: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,ValentynOn Thu, Aug 2, 2018 at 10:07 PM Suneel Marthi <smarthi@xxxxxxxxxx> wrote:+1 non-binding1. tested with beam samples2. verified sigs and hashes of artifactsOn 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
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
> * JIRA release notes ,
> * the official Apache source release to be deployed to dist.apache.org
> <http://dist.apache.org> , which is signed with the key with
> fingerprint 2F1FEDCDF6DD7990422F482F65224E0292DD8A51 ,
> * all artifacts to be deployed to the Maven Central Repository ,
> * source code tag "v2.6.0-RC1" ,
> * website pull request listing the release and publishing the API
> reference manual .
> * Python artifacts are deployed along with the source release to the
> dist.apache.org <http://dist.apache.org> .
> The vote will be open for at least 72 hours. It is adopted by majority
> approval, with at least 3 PMC affirmative votes.
>  https://dist.apache.org/repos/dist/dev/beam/2.6.0/
>  https://dist.apache.org/repos/dist/dev/beam/KEYS
>  https://repository.apache.org/content/repositories/orgapachebeam-1044/
>  https://github.com/apache/beam/tree/v2.6.0-RC1
>  https://github.com/apache/beam-site/pull/518
> Got feedback? go/pabloem-feedback
Talend - http://www.talend.com