You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by Henry Saginor <hs...@gmail.com> on 2020/08/14 05:51:48 UTC
sling npm release process
Hi,
The slingpackager [1] is a nodejs based tool for managing content packages. I would like to start publishing it on npmjs.org <http://npmjs.org/>.
I understand that there is apache-sling org on npmjs.org. But since slingpackager the first Sling nodejs module we don’t really have a process for this.
I want to start a discussion here to define it.
Please feel free to respond with any thoughts you may have. I know this is really open ended. :)
Henry
1. https://github.com/apache/sling-slingpackager
Re: sling npm release process
Posted by Robert Munteanu <ro...@apache.org>.
Hi Henry,
On Tue, 2020-12-29 at 15:16 -0800, Henry Saginor wrote:
> Sorry for a delay but I finally had some time to work on this. So,
> what is the process for uploading a release to dist.apache.org <
> http://dist.apache.org/>?
Have you seen [1]? This is our current process, based on the official
ASF release policy [2].
> According to release policy only PMC members can upload a release.
>
> Also, I have committed my work related to packaging and release
> process for slingpackager to this branch for now
> https://github.com/apache/sling-slingpackager/tree/travisBuild
> if anyone has time and is interested in review and feedback that’s
> always welcome
Out of curiosity, why Travis? We use Jenkins + the declarative pipeline
with good results.
Thanks,
Robert
[1]: https://sling.apache.org/documentation/development/release-management.html
[2]: https://www.apache.org/legal/release-policy.html
>
> > On Aug 14, 2020, at 6:21 AM, Robert Munteanu <ro...@apache.org>
> > wrote:
> >
> > Hi Henry,
> >
> > On Thu, 2020-08-13 at 22:51 -0700, Henry Saginor wrote:
> > > Hi,
> > >
> > > The slingpackager [1] is a nodejs based tool for managing content
> > > packages. I would like to start publishing it on npmjs.org <
> > > http://npmjs.org/>;.
> > > I understand that there is apache-sling org on npmjs.org. But
> > > since
> > > slingpackager the first Sling nodejs module we don’t really have
> > > a
> > > process for this.
> > > I want to start a discussion here to define it.
> >
> > I guess the first step would be to check how others at the ASF do
> > it.
> > Betrand has found some references and pasted them at
> >
> >
> > https://issues.apache.org/jira/browse/SLING-8747?focusedCommentId=16942825&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16942825
> >
> > Openwhisk also releases to npm, at least judging from
> >
> > https://github.com/apache/openwhisk-client-js
> >
> > As for the release requiements, the entry point is
> >
> > http://www.apache.org/legal/release-policy.html#artifacts
> >
> > . Briefly, that says:
> >
> > - include a source package that can be used to build and test the
> > release
> > - cryptographically sign the artifacts
> > - include LICENSE (and NOTICE if needed)
> > - include license headers
> >
> > A release must be published to dist.apache.org and _can_ be
> > published
> > to other channels like npmjs.org .
> >
> > Hopefully that is enough to start with, but let me know if you have
> > any
> > other questions.
> >
> > Oh, and I tried to add you to the npmjs org, but the site keeps
> > erroring out today. I'll try again later.
> >
> > Thanks,
> > Robert
> >
>
Re: sling npm release process
Posted by Henry Saginor <hs...@gmail.com>.
Sorry for a delay but I finally had some time to work on this. So, what is the process for uploading a release to dist.apache.org <http://dist.apache.org/>?
According to release policy only PMC members can upload a release.
Also, I have committed my work related to packaging and release process for slingpackager to this branch for now
https://github.com/apache/sling-slingpackager/tree/travisBuild
if anyone has time and is interested in review and feedback that’s always welcome
Thank You.
Happy New Year!
Henry
> On Aug 14, 2020, at 6:21 AM, Robert Munteanu <ro...@apache.org> wrote:
>
> Hi Henry,
>
> On Thu, 2020-08-13 at 22:51 -0700, Henry Saginor wrote:
>> Hi,
>>
>> The slingpackager [1] is a nodejs based tool for managing content
>> packages. I would like to start publishing it on npmjs.org <
>> http://npmjs.org/>;.
>> I understand that there is apache-sling org on npmjs.org. But since
>> slingpackager the first Sling nodejs module we don’t really have a
>> process for this.
>> I want to start a discussion here to define it.
>
> I guess the first step would be to check how others at the ASF do it.
> Betrand has found some references and pasted them at
>
> https://issues.apache.org/jira/browse/SLING-8747?focusedCommentId=16942825&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16942825
>
> Openwhisk also releases to npm, at least judging from
>
> https://github.com/apache/openwhisk-client-js
>
> As for the release requiements, the entry point is
>
> http://www.apache.org/legal/release-policy.html#artifacts
>
> . Briefly, that says:
>
> - include a source package that can be used to build and test the
> release
> - cryptographically sign the artifacts
> - include LICENSE (and NOTICE if needed)
> - include license headers
>
> A release must be published to dist.apache.org and _can_ be published
> to other channels like npmjs.org .
>
> Hopefully that is enough to start with, but let me know if you have any
> other questions.
>
> Oh, and I tried to add you to the npmjs org, but the site keeps
> erroring out today. I'll try again later.
>
> Thanks,
> Robert
>
Re: sling npm release process
Posted by Henry Saginor <hs...@gmail.com>.
Hi Robert,
Yes, I got. I have this org now. Thanks.
I think following ASF process should sufficient to start. I will try to get familiar with how other projects do this over the weekend as well.
Henry
> On Aug 14, 2020, at 9:07 AM, Robert Munteanu <ro...@apache.org> wrote:
>
> On Fri, 2020-08-14 at 15:21 +0200, Robert Munteanu wrote:
>> Oh, and I tried to add you to the npmjs org, but the site keeps
>> erroring out today. I'll try again later.
>
> Henry: you should've gotten an invite to the apache-sling org.
> Robert
>
Re: sling npm release process
Posted by Robert Munteanu <ro...@apache.org>.
On Fri, 2020-08-14 at 15:21 +0200, Robert Munteanu wrote:
> Oh, and I tried to add you to the npmjs org, but the site keeps
> erroring out today. I'll try again later.
Henry: you should've gotten an invite to the apache-sling org.
Robert
Re: sling npm release process
Posted by Robert Munteanu <ro...@apache.org>.
Hi Henry,
On Thu, 2020-08-13 at 22:51 -0700, Henry Saginor wrote:
> Hi,
>
> The slingpackager [1] is a nodejs based tool for managing content
> packages. I would like to start publishing it on npmjs.org <
> http://npmjs.org/>;.
> I understand that there is apache-sling org on npmjs.org. But since
> slingpackager the first Sling nodejs module we don’t really have a
> process for this.
> I want to start a discussion here to define it.
I guess the first step would be to check how others at the ASF do it.
Betrand has found some references and pasted them at
https://issues.apache.org/jira/browse/SLING-8747?focusedCommentId=16942825&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16942825
Openwhisk also releases to npm, at least judging from
https://github.com/apache/openwhisk-client-js
As for the release requiements, the entry point is
http://www.apache.org/legal/release-policy.html#artifacts
. Briefly, that says:
- include a source package that can be used to build and test the
release
- cryptographically sign the artifacts
- include LICENSE (and NOTICE if needed)
- include license headers
A release must be published to dist.apache.org and _can_ be published
to other channels like npmjs.org .
Hopefully that is enough to start with, but let me know if you have any
other questions.
Oh, and I tried to add you to the npmjs org, but the site keeps
erroring out today. I'll try again later.
Thanks,
Robert