I asked a question on how to use ASF publisher(vendor) for the VSCode
marketplace to the NetBeans community and got an answer.

We can register a VSCode contributor account according to this step:
https://issues.apache.org/jira/browse/INFRA-21017

I'll open a new INFRA ticket to register my account as a contributor and
get ready to make an extension releasing pipeline.

And for the JetBrains market, there is no ASF vendor, so I think a new ASF
vendor needs to be created.

Best regards
Seonghyun


2021년 4월 23일 (금) 오전 10:22, Seong Hyun Oh <seonghyu...@gmail.com>님이 작성:

>
> Hi dave,
>
> Thanks for your advice. I'll contact the Apache NetBeans community to find
> out how to deploy it to the marketplace and build a binary release job for
> plugins.
>
> Best regards
> Seonghyun
>
> 2021년 4월 23일 (금) 오전 6:52, David P Grove <gro...@us.ibm.com>님이 작성:
>
>>
>>
>>
>> Seong Hyun Oh <seonghyu...@gmail.com> wrote on 04/21/2021 05:03:25 AM:
>> >
>> > I'd like to release the openwhisk IDE plugins for vscode and Intellij
>> > according to the official Apache OpenWhisk project's Release Manager [1]
>> > and publish it to the marketplace. (We have published IDE plugins under
>> the
>> > NAVER vendor[2][3].)
>> >
>> > So I'd like to create a release procedure for those IDE plugin
>> repositories
>> > first, it would be appreciated if you let us know if IDE plugins can be
>> > managed with the openwhisk release manager and if Apache vendor can be
>> used
>> > to deploy IDE plugins to the market place (Microsoft VSCode and
>> Jetbrains).
>> >
>>
>> Hi,
>>
>>         The steps of making a source release are going to be roughly the
>> same
>> no matter what additional places we chose to make "convenience binaries"
>> available afterwards.
>>
>>         I took a quick look at the VSCode Marketplace and it looks like
>> Apache NetBeans is publishing their plugin using an official looking ASF
>> vendor. Probably the thing to do is to reach out to the community to find
>> out the details for how to also publish our plugin under that vendor.
>>
>> --dave
>>
>

Reply via email to