Agree to move forward on a PoC.
Thanks Reuven for bringing discussion on the mailing list !
Regards
JB
On Nov 1, 2017, 03:20, at 03:20, Reuven Lax wrote:
>Some good discussion here, and thanks to JB and Romain for adding to
>it!
>
>JB makes the good point that we still need to release Maven art
+1
It sounds like a good workflow to track the state of ideas/proposals.
Regards
JB
On Nov 1, 2017, 05:43, at 05:43, Reuven Lax wrote:
>There is a new JIRA workflow for tracking pending proposals. This
>workflow
>is described in https://issues.apache.org/jira/browse/INFRA-12698.
>Please
>vote o
There is a new JIRA workflow for tracking pending proposals. This workflow
is described in https://issues.apache.org/jira/browse/INFRA-12698. Please
vote on whether you believe Beam should adopt this new workflow.
Thanks,
Reuven
Hi everyone,
Please review and vote on the release candidate #2 for the version 2.2.0,
as follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)
The complete staging area is available for your review, which includes:
* JIRA release notes
Some good discussion here, and thanks to JB and Romain for adding to it!
JB makes the good point that we still need to release Maven artifacts, as
many Beam users want to develop using Maven. So none of this discussion
will affect our release process, as we still need Maven "releases."
At this po
Hi Guys,
I recently joined Google and will be contributing to Apache Beam project.
Please add me to the apache jira. My jira id is angoenka
Looking forward to work with you guys!
Thanks,
Ankur
Starting the RC2 cut now
On Tue, Oct 31, 2017 at 3:29 PM, Valentyn Tymofieiev <
valen...@google.com.invalid> wrote:
> At this point it's safe to proceed cutting the RC2, I don't anticipate
> further changes to release branch to resolve the blocking issues.
>
> On Mon, Oct 30, 2017 at 10:35 PM, Je
At this point it's safe to proceed cutting the RC2, I don't anticipate
further changes to release branch to resolve the blocking issues.
On Mon, Oct 30, 2017 at 10:35 PM, Jean-Baptiste Onofré
wrote:
> Great. Thanks for the update.
>
> Regards
> JB
>
> On Oct 31, 2017, 01:04, at 01:04, Eugene Kir
As a contributor to the Beam Python SDK, I noticed that many of the points
above regarding Maven and Gradle pertain mostly to Java SDK development.
For Python development, Maven is much less natural, and we end up just
shelling out to perform builds and tests. For Python SDK (and upcoming Go
SDK d
+1, Maven is both a build tool and a repository, and the latter is
essential to keep. Both Gradel and Bazel can interface with this
repository.
I am, however, very supportive of moving away from Maven to a tool
that supports correct incremental, hermetic, dependency-driven,
multi-langauge, and hop
Echoing what JB and Reuven said, we absolutely must provide maven central
artifacts for Java users, just as we provide pypi artifacts for Python
users.
I see Maven as still a viable tool for single-module Java builds,
especially considering its rich plugin ecosystem.
On Mon, Oct 30, 2017 at 11:27
We edited the "Roadmap" section a little bit to reflect our state of
knowledge. As before, all comments are welcome.
Thank you in advance!
2017-10-27 5:10 GMT+02:00 Kenneth Knowles :
> I am really excited about this development. Glad to have such a detailed
> document! Thanks for taking the time
Hmm,
so the incremenal support is mainly in "shared" libs - which means not
final plugins - but this is a work to do by plugin and not doable by
maven core which can't do it by itself correctly - so can be worth
opening an issue on plugins. Did you check gradle findbugs support was
better and stil
13 matches
Mail list logo
