damccorm merged PR #665:
URL: https://github.com/apache/beam-site/pull/665
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
I'm happy to announce that we have unanimously approved this release.
There are 7 approving votes, 3 of which are binding:
* Jan Lukavský (binding)
* Chamikara Jayalath (binding)
* Valentyn Tymofieiev (binding)
* XQ Hu
* Yi Hu
* Jeff Kinard
* Ritesh Ghorse
There are no disapproving votes. I will
unity members is
>>>>>> encouraged and helpful for finding regressions; you can either test your
>>>>>> own use cases [13] or use cases from the validation sheet [10].
>>>>>>
>>>>>> The complete staging area is available for y
>>> The complete staging area is available for your review, which includes:
>>>>> * GitHub Release notes [1],
>>>>> * the official Apache source release to be deployed to dist.apache.org
>>>>> [2], which is signed with the key with fingerprint D20316F71221
316F712213422 [3],
>>>> * all artifacts to be deployed to the Maven Central Repository [4],
>>>> * source code tag "v2.56.0-RC2" [5],
>>>> * website pull request listing the release [6], the blog post [6], and
>>>> publishing the API refe
ingerprint D20316F712213422 [3],
>>> * all artifacts to be deployed to the Maven Central Repository [4],
>>> * source code tag "v2.56.0-RC2" [5],
>>> * website pull request listing the release [6], the blog post [6], and
>>> publishing the API reference m
gt;> * website pull request listing the release [6], the blog post [6], and
>> publishing the API reference manual [7].
>> * Python artifacts are deployed along with the source release to the
>> dist.apache.org [2] and PyPI[8].
>> * Go artifacts and documentation are ava
> * website pull request listing the release [6], the blog post [6], and
> publishing the API reference manual [7].
> * Python artifacts are deployed along with the source release to the
> dist.apache.org [2] and PyPI[8].
> * Go artifacts and documentation are available at pkg.go.dev
g
[2] and PyPI[8].
* Go artifacts and documentation are available at pkg.go.dev [9]
* Validation sheet with a tab for 2.56.0 release to help
with validation [10].
* Docker images published to Docker Hub [11].
* PR to run test
gerprint D20316F712213422 [3],
>>> * all artifacts to be deployed to the Maven Central Repository [4],
>>> * source code tag "v2.56.0-RC2" [5],
>>> * website pull request listing the release [6], the blog post [6], and
>>> publishing the API reference
;> * all artifacts to be deployed to the Maven Central Repository [4],
>> * source code tag "v2.56.0-RC2" [5],
>> * website pull request listing the release [6], the blog post [6], and
>> publishing the API reference manual [7].
>> * Python artifacts are deployed alo
with the source release to
the dist.apache.org <http://dist.apache.org> [2] and PyPI[8].
* Go artifacts and documentation are available at pkg.go.dev
<http://pkg.go.dev> [9]
* Validation sheet with a tab for 2.56.0 release to help with
validation [10].
* Docker images
0-RC2" [5],
> * website pull request listing the release [6], the blog post [6], and
> publishing the API reference manual [7].
> * Python artifacts are deployed along with the source release to the
> dist.apache.org [2] and PyPI[8].
> * Go artifacts and documentation are availab
tion sheet with a tab for 2.56.0 release to help with validation
[10].
* Docker images published to Docker Hub [11].
* PR to run tests against release branch [12].
The vote will be open for at least 72 hours. It is adopted by majority
approval, with at least 3 PMC affirmative votes.
For guideli
damccorm closed pull request #664: Publish docs for 2.56.0 release
URL: https://github.com/apache/beam-site/pull/664
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment
e source release to
the dist.apache.org <http://dist.apache.org> [2] and PyPI[8].
* Go artifacts and documentation are available at pkg.go.dev
<http://pkg.go.dev> [9]
* Validation sheet with a tab for 2.56.0 release to help with
validation [10].
* Docker images
e source release to the
>> dist.apache.org [2] and PyPI[8].
>> * Go artifacts and documentation are available at pkg.go.dev [9]
>> * Validation sheet with a tab for 2.56.0 release to help with validation
>> [10].
>> * Docker images published to Docker Hub [11].
>> * PR to
[5],
> * website pull request listing the release [6], the blog post [6], and
> publishing the API reference manual [7].
> * Python artifacts are deployed along with the source release to the
> dist.apache.org [2] and PyPI[8].
> * Go artifacts and documentation are availab
tion sheet with a tab for 2.56.0 release to help with validation
[10].
* Docker images published to Docker Hub [11].
* PR to run tests against release branch [12].
The vote will be open for at least 72 hours. It is adopted by majority
approval, with at least 3 PMC affirmative votes.
For guideli
damccorm opened a new pull request, #664:
URL: https://github.com/apache/beam-site/pull/664
Content generated from https://github.com/apache/beam/tree/v2.56.0-RC1.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
a dev
>> wrote:
>>
>>> Hi,
>>>
>>> a nice round version number :)
>>>
>>> Cheers,
>>> Maciej
>>>
>>> On Thu, Apr 4, 2024 at 3:56 PM Danny McCormick via dev <
>>> dev@beam.apache.org> wrote:
>>&g
I just cut the release branch for the 2.56.0 release. There are still
several open issues for the milestone, some of which will require
cherry-picks [1], so there is still some time if you have urgent changes
that you would like to make the cut. I'll now move into stabilizing the
release branch [2
>>
>> On top of running the current 2.55.1 patch release, I'd like to volunteer
>> as release manager for the 2.56.0 release, which will be cut on April 17.
>> Please add any release blockers to the 2.56.0 milestone [1], I will be
>> trying to push on those as the cut dat
Hi,
a nice round version number :)
Cheers,
Maciej
On Thu, Apr 4, 2024 at 3:56 PM Danny McCormick via dev
wrote:
> Hey everyone,
>
> On top of running the current 2.55.1 patch release, I'd like to volunteer
> as release manager for the 2.56.0 release, which will be cut on April
Hey everyone,
On top of running the current 2.55.1 patch release, I'd like to volunteer
as release manager for the 2.56.0 release, which will be cut on April 17.
Please add any release blockers to the 2.56.0 milestone [1], I will be
trying to push on those as the cut date approaches.
Thanks
25 matches
Mail list logo
