[
https://issues.apache.org/jira/browse/CB-7930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Gill updated CB-7930:
---------------------------
Description:
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
was:
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)
- generate release notes for tools repos
- Get manual curation for changes in releasenotes
- Update package.json files + relevant dependencies
- npm link relevant repos
- run tests
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
> 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: Coho
> Reporter: Steve Gill
> Assignee: Steve Gill
>
> 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
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
