Re: Stop publishing unneeded Java artifacts

[Lukasz Cwik]

I wanted to double check that we don't rely on this publishing inside
Google for some reason. Will update this thread tomorrow.

On Wed, Aug 28, 2019 at 7:11 AM Łukasz Gajowy  wrote:

> Hi all,
>
> I wanted to notify that in PR 9417
>  I'm planning to turn off
> publishing of the following modules' artifacts to the maven repository:
>
>- :runners:google-cloud-dataflow-java:worker:windmill
>- :sdks:java:build-tools
>- :sdks:java:javadoc
>- :sdks:java:testing:expansion-service
>- :sdks:java:io:bigquery-io-perf-tests
>- :sdks:java:io:file-based-io-tests
>- :sdks:java:io:elasticsearch-tests:elasticsearch-tests-2
>- :sdks:java:io:elasticsearch-tests:elasticsearch-tests-5
>- :sdks:java:io:elasticsearch-tests:elasticsearch-tests-6
>- :sdks:java:io:elasticsearch-tests:elasticsearch-tests-common
>- :sdks:java:testing:load-tests
>- :sdks:java:testing:nexmark
>- :sdks:java:testing:test-utils
>
> AFAIK, the purpose of these modules is to keep related
> tests/test-utils/utils together. We are not expecting users to make use of
> such artifacts. Please let me know if you have any objections. If there are
> none and the PR gets merged, the artifacts will no longer be published.
>
> Thanks!
> Łukasz
>

Re: [PROPOSAL] Preparing for Beam 2.16.0 release

[Connell O'Callaghan]

+1 Mark - thank you and also all who support these releases by validating
the release etc!!!

On Thu, Aug 29, 2019 at 9:00 PM Lukasz Cwik  wrote:

> +1
>
> On Thu, Aug 29, 2019 at 7:42 PM Alan Myrvold  wrote:
>
>> +1 Thanks for keeping to the schedule, Mark.
>>
>> On Thu, Aug 29, 2019 at 6:21 PM jincheng sun 
>> wrote:
>>
>>> Hi Mark,
>>>
>>> +1 and thank you for keeping the cadence!
>>>
>>> BTW I have mark the Fix Version for some of issues to 2.17, which can
>>> not be merged into 2.16.
>>>
>>> Best,
>>> Jincheng
>>>
>>> Mark Liu  于2019年8月29日周四 上午6:14写道：
>>>
 Hi all,

 Beam 2.16 release branch cut is scheduled on Sep 11 according to the
 release calendar [1]. I would like to volunteer myself to do this
 release. The plan is to cut the branch on that date, and cherrypick
 release-blocking fixes afterwards if any.

 If you have release blocking issues for 2.16 please mark their "Fix
 Version" as 2.16.0 [2]. This tag is already created in JIRA in case you
 would like to move any non-blocking issues to that version.

 Any thoughts, comments, objections?

 Regards.
 Mark Liu

 [1]
 https://calendar.google.com/calendar/embed?src=0p73sl034k80oob7seouanigd0%40group.calendar.google.com
 [2]
 https://issues.apache.org/jira/browse/BEAM-8105?jql=project%20%3D%20BEAM%20AND%20status%20in%20(Reopened%2C%20Open%2C%20%22In%20Progress%22%2C%20%22Under%20Discussion%22%2C%20%22In%20Implementation%22%2C%20%22Triage%20Needed%22)%20AND%20fixVersion%20%3D%202.16.0

>>>

Re: [PROPOSAL] Preparing for Beam 2.16.0 release

[Lukasz Cwik]

+1

On Thu, Aug 29, 2019 at 7:42 PM Alan Myrvold  wrote:

> +1 Thanks for keeping to the schedule, Mark.
>
> On Thu, Aug 29, 2019 at 6:21 PM jincheng sun 
> wrote:
>
>> Hi Mark,
>>
>> +1 and thank you for keeping the cadence!
>>
>> BTW I have mark the Fix Version for some of issues to 2.17, which can
>> not be merged into 2.16.
>>
>> Best,
>> Jincheng
>>
>> Mark Liu  于2019年8月29日周四 上午6:14写道：
>>
>>> Hi all,
>>>
>>> Beam 2.16 release branch cut is scheduled on Sep 11 according to the
>>> release calendar [1]. I would like to volunteer myself to do this
>>> release. The plan is to cut the branch on that date, and cherrypick
>>> release-blocking fixes afterwards if any.
>>>
>>> If you have release blocking issues for 2.16 please mark their "Fix
>>> Version" as 2.16.0 [2]. This tag is already created in JIRA in case you
>>> would like to move any non-blocking issues to that version.
>>>
>>> Any thoughts, comments, objections?
>>>
>>> Regards.
>>> Mark Liu
>>>
>>> [1]
>>> https://calendar.google.com/calendar/embed?src=0p73sl034k80oob7seouanigd0%40group.calendar.google.com
>>> [2]
>>> https://issues.apache.org/jira/browse/BEAM-8105?jql=project%20%3D%20BEAM%20AND%20status%20in%20(Reopened%2C%20Open%2C%20%22In%20Progress%22%2C%20%22Under%20Discussion%22%2C%20%22In%20Implementation%22%2C%20%22Triage%20Needed%22)%20AND%20fixVersion%20%3D%202.16.0
>>>
>>

Re: [PROPOSAL] Preparing for Beam 2.16.0 release

[Ahmet Altay]

+1, thank you for keeping the cadence.

On Thu, Aug 29, 2019 at 7:42 PM Alan Myrvold  wrote:

> +1 Thanks for keeping to the schedule, Mark.
>
> On Thu, Aug 29, 2019 at 6:21 PM jincheng sun 
> wrote:
>
>> Hi Mark,
>>
>> +1 and thank you for keeping the cadence!
>>
>> BTW I have mark the Fix Version for some of issues to 2.17, which can
>> not be merged into 2.16.
>>
>> Best,
>> Jincheng
>>
>> Mark Liu  于2019年8月29日周四 上午6:14写道：
>>
>>> Hi all,
>>>
>>> Beam 2.16 release branch cut is scheduled on Sep 11 according to the
>>> release calendar [1]. I would like to volunteer myself to do this
>>> release. The plan is to cut the branch on that date, and cherrypick
>>> release-blocking fixes afterwards if any.
>>>
>>> If you have release blocking issues for 2.16 please mark their "Fix
>>> Version" as 2.16.0 [2]. This tag is already created in JIRA in case you
>>> would like to move any non-blocking issues to that version.
>>>
>>> Any thoughts, comments, objections?
>>>
>>> Regards.
>>> Mark Liu
>>>
>>> [1]
>>> https://calendar.google.com/calendar/embed?src=0p73sl034k80oob7seouanigd0%40group.calendar.google.com
>>> [2]
>>> https://issues.apache.org/jira/browse/BEAM-8105?jql=project%20%3D%20BEAM%20AND%20status%20in%20(Reopened%2C%20Open%2C%20%22In%20Progress%22%2C%20%22Under%20Discussion%22%2C%20%22In%20Implementation%22%2C%20%22Triage%20Needed%22)%20AND%20fixVersion%20%3D%202.16.0
>>>
>>

Re: [PROPOSAL] Preparing for Beam 2.16.0 release

[Alan Myrvold]

+1 Thanks for keeping to the schedule, Mark.

On Thu, Aug 29, 2019 at 6:21 PM jincheng sun 
wrote:

> Hi Mark,
>
> +1 and thank you for keeping the cadence!
>
> BTW I have mark the Fix Version for some of issues to 2.17, which can not
> be merged into 2.16.
>
> Best,
> Jincheng
>
> Mark Liu  于2019年8月29日周四 上午6:14写道：
>
>> Hi all,
>>
>> Beam 2.16 release branch cut is scheduled on Sep 11 according to the
>> release calendar [1]. I would like to volunteer myself to do this
>> release. The plan is to cut the branch on that date, and cherrypick
>> release-blocking fixes afterwards if any.
>>
>> If you have release blocking issues for 2.16 please mark their "Fix
>> Version" as 2.16.0 [2]. This tag is already created in JIRA in case you
>> would like to move any non-blocking issues to that version.
>>
>> Any thoughts, comments, objections?
>>
>> Regards.
>> Mark Liu
>>
>> [1]
>> https://calendar.google.com/calendar/embed?src=0p73sl034k80oob7seouanigd0%40group.calendar.google.com
>> [2]
>> https://issues.apache.org/jira/browse/BEAM-8105?jql=project%20%3D%20BEAM%20AND%20status%20in%20(Reopened%2C%20Open%2C%20%22In%20Progress%22%2C%20%22Under%20Discussion%22%2C%20%22In%20Implementation%22%2C%20%22Triage%20Needed%22)%20AND%20fixVersion%20%3D%202.16.0
>>
>

Re: [PROPOSAL] Preparing for Beam 2.16.0 release

[jincheng sun]

Hi Mark,

+1 and thank you for keeping the cadence!

BTW I have mark the Fix Version for some of issues to 2.17, which can not
be merged into 2.16.

Best,
Jincheng

Mark Liu  于2019年8月29日周四 上午6:14写道：

> Hi all,
>
> Beam 2.16 release branch cut is scheduled on Sep 11 according to the
> release calendar [1]. I would like to volunteer myself to do this
> release. The plan is to cut the branch on that date, and cherrypick
> release-blocking fixes afterwards if any.
>
> If you have release blocking issues for 2.16 please mark their "Fix
> Version" as 2.16.0 [2]. This tag is already created in JIRA in case you
> would like to move any non-blocking issues to that version.
>
> Any thoughts, comments, objections?
>
> Regards.
> Mark Liu
>
> [1]
> https://calendar.google.com/calendar/embed?src=0p73sl034k80oob7seouanigd0%40group.calendar.google.com
> [2]
> https://issues.apache.org/jira/browse/BEAM-8105?jql=project%20%3D%20BEAM%20AND%20status%20in%20(Reopened%2C%20Open%2C%20%22In%20Progress%22%2C%20%22Under%20Discussion%22%2C%20%22In%20Implementation%22%2C%20%22Triage%20Needed%22)%20AND%20fixVersion%20%3D%202.16.0
>

Re: [VOTE] Vendored Dependencies Release

[Rui Wang]

Thanks Kai and Andrew. Now prgapachebeam-1083 is publicly exposed.

I also found a useful link[1] to explain staging repos in Apache Nexus


[1]:
https://help.sonatype.com/repomanager2/staging-releases/managing-staging-repositories#ManagingStagingRepositories-ClosinganOpenRepository

-Rui

On Wed, Aug 28, 2019 at 9:19 PM Andrew Pilloud  wrote:

> You need to close the release for it to be published to the staging
> server. I can help if you still have questions.
>
> Andrew
>
> On Wed, Aug 28, 2019, 8:48 PM Rui Wang  wrote:
>
>> I can see prgapachebeam-1083 is in open status in staging repository. I
>> am not sure why it is not public exposed. I probably need some guidance on
>> it.
>>
>>
>> -Rui
>>
>> On Wed, Aug 28, 2019 at 3:50 PM Kai Jiang  wrote:
>>
>>> Hi Rui,
>>>
>>> For accessing artifacts [1] in Maven Central Repository, is this intent
>>> to be not public exposed?
>>>
>>> Best,
>>> Kai
>>>
>>> [1]
>>> https://repository.apache.org/content/repositories/orgapachebeam-1083/
>>>
>>> On Wed, Aug 28, 2019 at 11:57 AM Kai Jiang  wrote:
>>>
 +1 (non-binding)Thanks Rui!

 On Tue, Aug 27, 2019 at 10:46 PM Rui Wang  wrote:

> Please review the release of the following artifacts that we vendor:
>
>  * beam-vendor-calcite-1_20_0
>
> Hi everyone,
>
> Please review and vote on the release candidate #1 for the
> org.apache.beam:beam-vendor-calcite-1_20_0:0.1, 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:
>
> * the official Apache source release to be deployed to dist.apache.org
> [1], which is signed with the key with fingerprint
> 0D7BE1A252DBCEE89F6491BBDFA64862B703F5C8 [2],
>
> * all artifacts to be deployed to the Maven Central Repository [3],
>
> * commit hash "664e25019fc1977e7041e4b834e8d9628b912473" [4],
>
> The vote will be open for at least 72 hours. It is adopted by majority
> approval, with at least 3 PMC affirmative votes.
>
> Thanks,
>
> Rui
>
> [1] https://dist.apache.org/repos/dist/dev/beam/vendor/calcite/1_20_0
>
> [2] https://dist.apache.org/repos/dist/release/beam/KEYS
>
> [3]
> https://repository.apache.org/content/repositories/orgapachebeam-1083/
>
> [4]
> https://github.com/apache/beam/commit/664e25019fc1977e7041e4b834e8d9628b912473
>
>

Re: Hackathon @BeamSummit @ApacheCon

[Maximilian Michels]

Hey,

I'm in as well! Austin and I recently talked about how we could organize 
the hackathon. Likely it will be an hour per day for exchanging ideas 
and learning about Beam. For example, there has been interest from the 
Apache Streams project to discuss points for collaboration.


We will soon announce the exact hours.

Cheers,
Max

On 23.08.19 05:06, Kenneth Knowles wrote:
I will be at Beam Summit / ApacheCon NA and would love to drop by a 
hackathon room if one is arranged. Really excited for both my first 
ApacheCon and Beam Summit (finally!)


Kenn

On Thu, Aug 22, 2019 at 10:18 AM Austin Bennett 
mailto:whatwouldausti...@gmail.com>> wrote:


And, for clarity, especially focused on Hackathon times on Monday
and/or Tuesday of ApacheCon, to not conflict with BeamSummit sessions.

On Thu, Aug 22, 2019 at 9:47 AM Austin Bennett
mailto:whatwouldausti...@gmail.com>>
wrote:

Less than 3 weeks till Beam Summit @ApacheCon!

We are to be in Vegas for BeamSummit and ApacheCon in a few weeks.

Likely to reserve space in the Hackathon Room to accomplish some
tasks:
* Help Users
* Build Beam
* Collaborate with other projects
* etc

If you're to be around (or not) let us know how you'd like to be
involved.  Also, please share and surface anything that would be
good for us to look at (and, esp. any beginner tasks, in case we
can entice some new contributors).


P.S.  See BeamSummit.org, if you're thinking of attending -
there's a discount code.