[RESULT] [VOTE] JupyterLab Sidepanel extension release v1.0.0 for BEAM-10545 RC #1

2020-10-19 Thread Ning Kang 
I'm happy to announce that we have unanimously approved this release.

There are 3 approving votes, all of which are binding:
* Ahmet Altay
* Pablo Estrada
* Robert Bradshaw

There are no disapproving votes.

Thanks everyone!


On Fri, Oct 16, 2020 at 2:05 PM Robert Bradshaw  wrote:

> Thanks, Ning and Ahmet.
>
> +1 (binding) Approve the release.
>
> On Fri, Oct 16, 2020 at 1:34 PM Ning Kang  wrote:
>
>> Sorry, if you cannot see the missing thread history in the previous
>> thread, here is another copy:
>>
>> On Fri, Oct 16, 2020 at 9:55 AM Robert Bradshaw 
>> wrote:
>>
>>> Thanks.
>>>
>>> +1 (binding) to this release.
>>>
>>> On Thu, Oct 15, 2020 at 7:06 PM Ahmet Altay  wrote:
>>>
 Here you go:
 https://dist.apache.org/repos/dist/dev/beam/extensions/jupyterlab-sidepanel/v1.0.0/

 On Thu, Oct 15, 2020 at 5:11 PM Robert Bradshaw 
 wrote:

> If we can stage the sources to dist/dev that sounds good to me.
>
> On Thu, Oct 15, 2020 at 4:57 PM Ning Kang  wrote:
>
>> +1 to Ahmet's suggestion.
>>
>> I've taken a look at the process
>> 
>>  used
>> by vendored artifacts and summarized below commands to stage the source
>> code to dist/dev
>>
>> extension=jupyterlab-sidepanel
>>
>> version=v1.0.0
>>
>> tag=${extension}-${version}
>>
>>
>> svn co https://dist.apache.org/repos/dist/dev/beam
>>
>> mkdir -p beam/extensions/${extension}/${version}
>>
>> pushd beam/extensions/${extension}/${version}
>>
>> curl -o apache-beam-${tag}-source-release.zip https://
>> github.com/apache/beam/archive/${tag}.zip
>> 
>>
>> gpg --armor --detach-sig apache-beam-${tag}-source-release.zip
>>
>> sha512sum apache-beam-${tag}-source-release.zip > apache-beam-${tag}-
>> source-release.zip.sha512
>>
>> # If sha512sum command is not found, on mac, run brew install
>> coreutils;
>>
>> # on linux, run apt-get install coreutils
>>
>> popd
>>
>> pushd beam
>>
>> # For the first time adding the directory with its contents
>>
>> svn add extensions
>>
>> # For future versions, use below to add
>>
>> # svn add extensions/${extension}/${version}
>>
>> svn commit
>>
>> Please feel free to comment on the directory structure.
>>
>> Ahmet, if everything looks good, could you please help me execute the
>> commands with your GPG key to stage the source to dist/dev?
>> And once we publish the extension to NPM, we'll move the source from
>> dist/dev to dist/release following the same process
>> 
>>  to
>> vendored artifact's releases.
>>
>> I'll document the release process with release history in the Beam
>> repo once the release is done.
>>
>> Thanks!
>>
>> On Thu, Oct 15, 2020 at 1:06 PM Ahmet Altay  wrote:
>>
>>> This is similar to the vendored dependencies release. For that we
>>> vote on the artifacts. commit hash, and staged source distribution on
>>> dist/dev[1]. And then the same source distribution is promoted to
>>> dist/release [2]. We can follow the same process and stage a source
>>> distribution to dist.
>>>
>>> [1]
>>> https://lists.apache.org/thread.html/rea4a27c47529a27936ab2c51162c8e532b8b625c4d70c4f7f485c7cd%40%3Cdev.beam.apache.org%3E
>>> [2] https://dist.apache.org/repos/dist/release/beam/vendor/
>>>
>>> On Thu, Oct 15, 2020 at 12:17 PM Robert Bradshaw <
>>> rober...@google.com> wrote:
>>>
 I'm thinking specifically of


 https://incubator.apache.org/guides/distribution.html#release_platforms

 In addition to the Apache mirror system incubating projects may
 distribute artifacts on other platforms as long as they follow these
 general guidelines:
 * Source releases must be placed in the Apache mirror system.


 On Thu, Oct 15, 2020 at 12:05 PM Ning Kang 
 wrote:

> Thanks Robert, I didn't know the existence of this document.
>
> Looks like the only thing potentially missing is the incubation
> disclaimer.
> NPM should be the only channel for distribution. And normally, a
> jupyter user would install extensions through `jupyter` commands. They
> wouldn't even use the `npm` command directly.
>
> Looking at
> https://incubator.apache.org/guides/branding.html#disclaimers,
> since this extension is part of Beam and we are not incubating 
> something
> new, we might not even need an incubation disclaimer.
>

Re: [RESULT] [VOTE] JupyterLab Sidepanel extension release v1.0.0 for BEAM-10545 RC #1

2020-10-19 Thread Ning Kang 
The package has been published to NPM:
https://www.npmjs.com/package/apache-beam-jupyterlab-sidepanel

Verified that JupyterLab v2+ users can use `jupyter labextension install
apache-beam-jupyterlab-sidepanel` to install it now.

Cheers!

On Mon, Oct 19, 2020 at 11:19 AM Ning Kang  wrote:

> I'm happy to announce that we have unanimously approved this release.
>
> There are 3 approving votes, all of which are binding:
> * Ahmet Altay
> * Pablo Estrada
> * Robert Bradshaw
>
> There are no disapproving votes.
>
> Thanks everyone!
>
>
> On Fri, Oct 16, 2020 at 2:05 PM Robert Bradshaw 
> wrote:
>
>> Thanks, Ning and Ahmet.
>>
>> +1 (binding) Approve the release.
>>
>> On Fri, Oct 16, 2020 at 1:34 PM Ning Kang  wrote:
>>
>>> Sorry, if you cannot see the missing thread history in the previous
>>> thread, here is another copy:
>>>
>>> On Fri, Oct 16, 2020 at 9:55 AM Robert Bradshaw 
>>> wrote:
>>>
 Thanks.

 +1 (binding) to this release.

 On Thu, Oct 15, 2020 at 7:06 PM Ahmet Altay  wrote:

> Here you go:
> https://dist.apache.org/repos/dist/dev/beam/extensions/jupyterlab-sidepanel/v1.0.0/
>
> On Thu, Oct 15, 2020 at 5:11 PM Robert Bradshaw 
> wrote:
>
>> If we can stage the sources to dist/dev that sounds good to me.
>>
>> On Thu, Oct 15, 2020 at 4:57 PM Ning Kang  wrote:
>>
>>> +1 to Ahmet's suggestion.
>>>
>>> I've taken a look at the process
>>> 
>>>  used
>>> by vendored artifacts and summarized below commands to stage the source
>>> code to dist/dev
>>>
>>> extension=jupyterlab-sidepanel
>>>
>>> version=v1.0.0
>>>
>>> tag=${extension}-${version}
>>>
>>>
>>> svn co https://dist.apache.org/repos/dist/dev/beam
>>>
>>> mkdir -p beam/extensions/${extension}/${version}
>>>
>>> pushd beam/extensions/${extension}/${version}
>>>
>>> curl -o apache-beam-${tag}-source-release.zip https://
>>> github.com/apache/beam/archive/${tag}.zip
>>> 
>>>
>>> gpg --armor --detach-sig apache-beam-${tag}-source-release.zip
>>>
>>> sha512sum apache-beam-${tag}-source-release.zip > apache-beam-${tag
>>> }-source-release.zip.sha512
>>>
>>> # If sha512sum command is not found, on mac, run brew install
>>> coreutils;
>>>
>>> # on linux, run apt-get install coreutils
>>>
>>> popd
>>>
>>> pushd beam
>>>
>>> # For the first time adding the directory with its contents
>>>
>>> svn add extensions
>>>
>>> # For future versions, use below to add
>>>
>>> # svn add extensions/${extension}/${version}
>>>
>>> svn commit
>>>
>>> Please feel free to comment on the directory structure.
>>>
>>> Ahmet, if everything looks good, could you please help me execute
>>> the commands with your GPG key to stage the source to dist/dev?
>>> And once we publish the extension to NPM, we'll move the source from
>>> dist/dev to dist/release following the same process
>>> 
>>>  to
>>> vendored artifact's releases.
>>>
>>> I'll document the release process with release history in the Beam
>>> repo once the release is done.
>>>
>>> Thanks!
>>>
>>> On Thu, Oct 15, 2020 at 1:06 PM Ahmet Altay 
>>> wrote:
>>>
 This is similar to the vendored dependencies release. For that we
 vote on the artifacts. commit hash, and staged source distribution on
 dist/dev[1]. And then the same source distribution is promoted to
 dist/release [2]. We can follow the same process and stage a source
 distribution to dist.

 [1]
 https://lists.apache.org/thread.html/rea4a27c47529a27936ab2c51162c8e532b8b625c4d70c4f7f485c7cd%40%3Cdev.beam.apache.org%3E
 [2] https://dist.apache.org/repos/dist/release/beam/vendor/

 On Thu, Oct 15, 2020 at 12:17 PM Robert Bradshaw <
 rober...@google.com> wrote:

> I'm thinking specifically of
>
>
> https://incubator.apache.org/guides/distribution.html#release_platforms
>
> In addition to the Apache mirror system incubating projects may
> distribute artifacts on other platforms as long as they follow these
> general guidelines:
> * Source releases must be placed in the Apache mirror system.
>
>
> On Thu, Oct 15, 2020 at 12:05 PM Ning Kang 
> wrote:
>
>> Thanks Robert, I didn't know the existence of this document.
>>
>> Looks like the only thing potentially missing is the incubation
>> disclaimer.
>> NPM should be the only c