[jira] [Closed] (CB-7930) create coho toolsRelease command based off nightly

["Bryan Ellis (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CB-7930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bryan Ellis closed CB-7930.
---------------------------
    Resolution: Won't Fix

I believe this request is no longer needed. There has been a lot of changes in release process since where some of the content is no longer valid.

> create coho toolsRelease command based off nightly
> --------------------------------------------------
>
>                 Key: CB-7930
>                 URL: https://issues.apache.org/jira/browse/CB-7930
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: cordova-coho
>            Reporter: Steve Gill
>            Priority: Major
>
> It will be based off coho nightly. Multi-step process. Proposal below. Still figuring out some details (what to pass in). Feel free to comment and provide feedback. 
> Step 1) coho prepare-tools-release --jira ISSUENUMBER
> - Use latest tags in platform repos; use in platformsConfig.json
> - Include cordova-js & plugman (nightlies don't)(cordova-js: only if changes exist)
> - Update package.json files + relevant dependencies
> - npm link relevant repos
> - run tests
> - generate release notes for tools repos
> - Ask user for manual curation for changes in release notes
> Step 2) coho publish-tools --rc --jira ISSUENUMBER
> - branch tools repos (no need to cherry-pick release log changes)
> - update versions on master with -dev
> - Commit changes
> - Build archive
> - publish archive to npm under rc tag
> - publish to dist/dev
> Step 3) (manual for now)
> - Start vote thread
> - close vote thread
> Step 4) coho publish-tools --final --jira ISSUENUMBER
> - Publish to dist & delete dist/dev
> - Change npm latest tags to point to new versions
> Not including for now:
> - Generating issue on Jira (should be done manually pre step 1)
> - Pinning dependencies (should be done manually pre step 1)
> - license checks (should be done manually pre step 1)
> - audit-license-headers (should be done manually pre step 1)
> - Changes to docs.cordova.io
> - Creating blog post



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@cordova.apache.org
For additional commands, e-mail: issues-help@cordova.apache.org