+1 (binding) The artifacts all look good to me.
On Wed, Apr 3, 2024 at 1:35 PM XQ Hu via dev wrote:
> +1 (non-binding). Tested this using a simple Dataflow ML pipeline:
> https://github.com/google/dataflow-ml-starter/actions/runs/8541848483.
>
> On Wed, Apr 3, 2024 at 2:35 PM Jeff Kinard
+1 (non-binding). Tested this using a simple Dataflow ML pipeline:
https://github.com/google/dataflow-ml-starter/actions/runs/8541848483.
On Wed, Apr 3, 2024 at 2:35 PM Jeff Kinard wrote:
> +1. Validated running from local gradle JAR and staged maven JAR for
> expansion-service.
>
> On Wed, Apr
+1. Validated running from local gradle JAR and staged maven JAR for
expansion-service.
On Wed, Apr 3, 2024 at 11:08 AM Danny McCormick via dev
wrote:
> Hi everyone,
>
> I put together a patch release per the conversation in
> https://lists.apache.org/thread/kvq1wsj505pvopkq186dnvc0l6ryyfh0.
>
+1 (binding)
Kenn
On Wed, Apr 3, 2024 at 12:58 PM Danny McCormick via dev
wrote:
> > Also noting that there is no PR postsubmit test suite running against
> the release branch in the vote email. Given the diff, that's also fine
> since previous tests runs didn't detect the breakage, but in
On Wed, Apr 3, 2024 at 4:15 AM Kenneth Knowles wrote:
> Let me summarize the most recent proposal on-list to frame my question
> about this last suggestion. It looks like this:
>
> 1. user has an element, call it `data`
> 2. user maps `data` to an arbitrary metadata row, call it `dest`
> 3. we
> Also noting that there is no PR postsubmit test suite running against the
release branch in the vote email. Given the diff, that's also fine since
previous tests runs didn't detect the breakage, but in general we should
include that for patch releases as well.
Yeah, it didn't seem useful to
damccorm opened a new pull request, #663:
URL: https://github.com/apache/beam-site/pull/663
Content generated from https://github.com/apache/beam/tree/v2.55.1-RC2.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
Hi Danny,
Thanks for volunteering to do this patch release.
For review convenience, this is the diff:
- Diff of release branches:
https://github.com/apache/beam/compare/release-2.55.0...release-2.55.1
- The diff of tags v2.55.0-RC3 and v2.55.1-RC2:
[Note: You're receiving this email because you are subscribed to one
or more project dev@ mailing lists at the Apache Software Foundation.]
Dear community,
We hope you are doing great, are you ready for Community Over Code EU?
Check out the featured sessions, get your tickets with special
Hi everyone,
I put together a patch release per the conversation in
https://lists.apache.org/thread/kvq1wsj505pvopkq186dnvc0l6ryyfh0.
Please review and vote on the release candidate #2 (I messed up rc1) for
the version 2.55.1, as follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the
Hi everyone,
As part of The ASF’s 25th anniversary campaign[1], we will be celebrating
projects and communities in multiple ways.
We invite all projects and contributors to participate in the following
ways:
* Individuals - submit your first contribution:
Let me summarize the most recent proposal on-list to frame my question
about this last suggestion. It looks like this:
1. user has an element, call it `data`
2. user maps `data` to an arbitrary metadata row, call it `dest`
3. we can do things like shuffle on `dest` because it isn't too big
4. we
This is your daily summary of Beam's current high priority issues that may need
attention.
See https://beam.apache.org/contribute/issue-priorities for the meaning and
expectations around issue priorities.
Unassigned P1 Issues:
https://github.com/apache/beam/issues/30820 [Bug]: Install
13 matches
Mail list logo
