Thanks, Pablo, much appreciated!
On Wed, Jul 29, 2020 at 3:44 PM Pablo Estrada wrote:
> I'll get on this. Thanks!
> -P.
>
> On Wed, Jul 29, 2020 at 3:40 PM Valentyn Tymofieiev
> wrote:
>
>> I need help from a PMC member to perform PMC-only actions in the release
>> guide[1].
>>
>> Also, a PMC c
I'll get on this. Thanks!
-P.
On Wed, Jul 29, 2020 at 3:40 PM Valentyn Tymofieiev
wrote:
> I need help from a PMC member to perform PMC-only actions in the release
> guide[1].
>
> Also, a PMC could help update the Docker Hub page for Python 3.8 [2],
> since we have released Py3.8 container image
I need help from a PMC member to perform PMC-only actions in the release
guide[1].
Also, a PMC could help update the Docker Hub page for Python 3.8 [2], since
we have released Py3.8 container images now. We can also remove references
to Apache Apex from this and other hub pages.
Thank you!
[1] h
Thank you, Kyle!
On Wed, Jul 8, 2020 at 10:03 AM Kyle Weaver wrote:
> > I may need help with a Samza ValidatesRunner failure [1]. It has been
> failing since at least June 24 [2].
>
> Looks like a duplicate of https://issues.apache.org/jira/browse/BEAM-10025
> .
>
> > 1. Did this issue come up d
> I may need help with a Samza ValidatesRunner failure [1]. It has been
failing since at least June 24 [2].
Looks like a duplicate of https://issues.apache.org/jira/browse/BEAM-10025.
> 1. Did this issue come up during earlier releases?
Yes, this affected the 2.21 and 2.22 releases. tl;dr it was
There are some test failures on the release branch that need to be
addressed.
I may need help with a Samza ValidatesRunner failure [1]. It has been
failing since at least June 24 [2].
1. Did this issue come up during earlier releases?
2. Do we know why this suite is not visible in Beam metrics da
So far the release process is going well.
Currently running several release validation suites[1], and plan to send
out an RC once these are completed.
Here is how the community can help:
1. If there is a test suite that you've added recently, but did not add it
to .test-infra/jenkins/README.md
<
Done.
On Wed, Jul 1, 2020 at 5:40 PM Valentyn Tymofieiev
wrote:
> Can somebody please add my pypi username (tvalentyn) to the list of
> apache-beam maintainers on PyPi: https://pypi.org/project/apache-beam/ ?
> Thank you!
>
> On Wed, Jul 1, 2020 at 4:51 PM Valentyn Tymofieiev
> wrote:
>
>> Rele
Can somebody please add my pypi username (tvalentyn) to the list of
apache-beam maintainers on PyPi: https://pypi.org/project/apache-beam/ ?
Thank you!
On Wed, Jul 1, 2020 at 4:51 PM Valentyn Tymofieiev
wrote:
> Release branch has been cut.
>
> As a reminder, please do not merge commits into the
Release branch has been cut.
As a reminder, please do not merge commits into the release branch
directly, instead, loop in the release manager if any cherry-picks are
required.
Thank you.
On Wed, Jul 1, 2020 at 9:25 AM Valentyn Tymofieiev
wrote:
> Great, thank you Tobiasz, I will take a look.
Great, thank you Tobiasz, I will take a look.
On Wed, Jul 1, 2020 at 7:27 AM Tobiasz Kędzierski <
tobiasz.kedzier...@polidea.com> wrote:
> Hi,
>
> I've just created PR introducing usage of GH-Actions to release process
> https://github.com/apache/beam/pull/12150
>
> Let me know what you think, ma
Hi,
I've just created PR introducing usage of GH-Actions to release process
https://github.com/apache/beam/pull/12150
Let me know what you think, maybe you have some suggestions on what may be
improved.
BR
Tobiasz
On Wed, Jul 1, 2020 at 6:08 AM Ahmet Altay wrote:
> Valentyn,
>
> +tobiasz.kedz
Valentyn,
+tobiasz.kedzier...@polidea.com added a
github action for building python wheel files (
https://github.com/apache/beam/pull/11877). You should be able to build the
wheel files using this github action instead of using the beam-wheels repo
and Travis. Please give it a try during the rele
Friendly reminder that the release cut is slated next week.
If you are aware of *release-blocking* issues, please open a JIRA and set
the "Fix version" to be 2.23.0.
Please do not set "Fix version" for open non-blocking issues, instead set
"Fix version" once the issue is actually resolved.
Thank
Thank you Valentyn!
On Mon, Jun 15, 2020 at 1:08 PM Ahmet Altay wrote:
> Thank you Valentyn!
>
> On Mon, Jun 15, 2020 at 12:46 PM Ankur Goenka wrote:
>
>> Thanks Valentyn!
>>
>> On Mon, Jun 15, 2020 at 12:41 PM Kyle Weaver wrote:
>>
>>> Sounds good, thanks Valentyn!
>>>
>>> On Mon, Jun 15, 202
Thank you Valentyn!
On Mon, Jun 15, 2020 at 12:46 PM Ankur Goenka wrote:
> Thanks Valentyn!
>
> On Mon, Jun 15, 2020 at 12:41 PM Kyle Weaver wrote:
>
>> Sounds good, thanks Valentyn!
>>
>> On Mon, Jun 15, 2020 at 12:31 PM Valentyn Tymofieiev
>> wrote:
>>
>>> Hi all,
>>>
>>> According to the Be
Thanks Valentyn!
On Mon, Jun 15, 2020 at 12:41 PM Kyle Weaver wrote:
> Sounds good, thanks Valentyn!
>
> On Mon, Jun 15, 2020 at 12:31 PM Valentyn Tymofieiev
> wrote:
>
>> Hi all,
>>
>> According to the Beam release calendar [1], the next (2.23.0) release
>> branch cut is scheduled for July 1.
Sounds good, thanks Valentyn!
On Mon, Jun 15, 2020 at 12:31 PM Valentyn Tymofieiev
wrote:
> Hi all,
>
> According to the Beam release calendar [1], the next (2.23.0) release
> branch cut is scheduled for July 1.
>
> I would be happy to help with this release and volunteer myself to be the
> next
Hi all,
According to the Beam release calendar [1], the next (2.23.0) release
branch cut is scheduled for July 1.
I would be happy to help with this release and volunteer myself to be the
next release manager.
As usual, the plan is to cut the branch on that date, and cherrypick release
-blocking
19 matches
Mail list logo
