Looks good. The steps 2&3 are best done after 5 in case the vote fails. The 
release vote is pinned to a commit hash. 

The steps documented and support scripts in the openwhisk-release help in 
getting these organized and executed. It will be very useful for a fresh pair 
of eyes to go through these as that usually leads to worthwhile improvements. 

-r

> On Mar 6, 2020, at 12:27 AM, Alexander Klimetschek 
> <aklim...@adobe.com.invalid> wrote:
> 
> Hi,
> 
> thanks to everyone who was helping, it looks like everything is in place for 
> an initial release of wskdebug!
> 
> AFAICS, the next steps would be:
> 
> 1. bump version to 1.2.0 in package.json via `npm version 1.2.0` (this also 
> creates a git tag v1.2.0)
> 2. push the git tag to github
> 3. edit the tag/release and add release notes like we did previously here [2]
>    - in this case nothing has changed, so it could just say something like:
>    - "Initial release under new Apache OpenWhisk ownership and new name 
> @openwhisk/wskdebug"
> 4. take the release source from github and prepare the release
> 5. run the release vote
> 6. once accepted, npm publish (as @openwhisk/wskdebug already set [3])
> 
> All of these would have to be done by committer(s).
> 
> Post release:
> 
> 7. I would deprecate the old @adobe/wskdebug on npm and point to the new 
> package
> 8. I would archive https://github.com/adobe/wskdebug
> 9. and consider the move done!
> 
> wdyt?
> 
> [1] https://github.com/apache/openwhisk-wskdebug
> [2] https://github.com/adobe/wskdebug/releases
> [3] https://github.com/apache/openwhisk-wskdebug/blob/master/package.json#L2
> 
> Cheers,
> Alex

Reply via email to