Hi All,
I did the implementation as you mentioned and created a PR (
https://github.com/apache/beam/pull/2216) for CI and also for code related
discussion. I'm writing unit tests for the code changes.
If you get time, please have a look at the code and provide the feedback.
Thanks in advance,
Fair enough, let's wait and as said, use the "First stable release" in Jira.
Regards
JB
On 03/09/2017 11:04 PM, Davor Bonaci wrote:
I added "First stable release" in JIRA as a version identifier a while
back, to avoid any prejudice what that version might be called. I think it
makes sense to
Thanks for the quick reply Kenneth. Currently I am going through *Apache
Beam* installation and referring Programming Guide and Documentation.
Please update me if their any suggestions.
On 10 March 2017 at 09:14, Kenneth Knowles wrote:
> Hi Milinda,
>
> Glad you are
bq. ran into a known issue [14]
Currently BEAM-1674 is marked blocker. Would it be pushed to next release ?
Cheers
On Thu, Mar 9, 2017 at 4:07 PM, Ahmet Altay
wrote:
> Hi everyone,
>
> Please review and vote on the release candidate #1 for the version 0.6.0,
> as
Hi Milinda,
Glad you are interested! I think it should be very fun and rewarding.
The student application period for Google Summer of Code opens on March
20th, so be sure to apply then.
I also recommend subscribing to
https://issues.apache.org/jira/browse/BEAM-1439. I will add some details
+1
Checked signature
Ran test suite - all passed.
On Thu, Mar 9, 2017 at 4:07 PM, Ahmet Altay
wrote:
> Hi everyone,
>
> Please review and vote on the release candidate #1 for the version 0.6.0,
> as follows:
> [ ] +1, Approve the release
> [ ] -1, Do not approve the
Hi, I'm Milinda Kasun, I am a Final year undergraduate from the Department
of Computer Science and Engineering (University of Moratuwa, Sri Lanka). I
have experience on development with Java and Python. I would like do this
project for GSoC 2017. It would be greatly appreciated if you could help
Hi everyone,
Please review and vote on the release candidate #1 for the version 0.6.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 [1],
*
I added "First stable release" in JIRA as a version identifier a while
back, to avoid any prejudice what that version might be called. I think it
makes sense to resolve (newly fixed) issues against that version. Once we
finalize the name of that release, we can easily rename it to either
"1.0.0"
We certainly cannot do this ourselves, but it is within the realm of
possibility that Apache Infra can assign tags to our GitHub repositories.
Looking at the tags that already exist, perhaps we could go with:
* apache-beam
* big-data
* data-processing
* data-analysis
* data-science
*
Well, for now at least. We have to use something for fixed issues..
On Thu, Mar 9, 2017 at 6:32 PM Jean-Baptiste Onofré wrote:
> By the way, waiting the end of this discussion, we can use "First stable
> release" as version in Jira.
>
> Regards
> JB
>
> On 03/09/2017 07:21
By the way, waiting the end of this discussion, we can use "First stable
release" as version in Jira.
Regards
JB
On 03/09/2017 07:21 AM, Jean-Baptiste Onofré wrote:
Hi all,
Release branch for 0.6.0 has been created but the next cycle version has
not been created in Jira.
I propose to create
Hi Aviem,
thanks for the hit !
I thought about reviewers feature too but it requires "write" access to
github, which is not possible as github is just a mirror of Apache git.
Regards
JB
On 03/09/2017 01:31 PM, Aviem Zur wrote:
About a month ago GitHub introduced topics, which let GitHub
About a month ago GitHub introduced topics, which let GitHub users query
for repositories by topics (domains that the repos deal with).
We can leverage these to increase Beam's exposure on GitHub.
Example topics we could add: big-data, google-cloud-dataflow, spark, flink,
apex, gearpump
We can
I'm looking into the recent streak of unstable builds.
- Original message -
From: Apache Jenkins Server
To: comm...@beam.apache.org, k...@google.com, al...@google.com
Subject: Jenkins build is still unstable:
beam_PostCommit_Java_RunnableOnService_Flink #1866
Hi all,
We had a discussion with Kenn yesterday about point 1 bellow, I would
like to note it here on the ML:
Using new method timer.set() instead of timer.setForNowPlus() makes the
timer fire at the right time.
Another thing, regarding point 2: if I inject the window in the @Ontimer
16 matches
Mail list logo