Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[WIP] CB-14249 ensure platform changes are in a dev version (partial workaround doc fix) #189

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions docs/platforms-release-process.md
Original file line number Diff line number Diff line change
Expand Up @@ -33,6 +33,7 @@ It describes the following steps:
- [Before you start](#before-you-start)
* [Read through Apache release policy](#read-through-apache-release-policy)
* [Request buy-in](#request-buy-in)
* [Ensure changes are in a dev version](#ensure-changes-are-in-a-dev-version)
- [Before Release](#before-release)
* [npm audit check](#npm-audit-check)
* [Check dependencies](#check-dependencies)
Expand Down Expand Up @@ -122,6 +123,10 @@ Double check you replace "Android" in the subject and mail body - there is no un

Note that it would be possible to continue with some of the [Before Release](#before-release) items while waiting for a possible response.

### Ensure changes are in a dev version

The procedure described here may leave non-master branch with a non-dev version number. Functional changes should always be done in a "-dev" version. Please mark the "-dev" version manually or using cordova-coho before making changes, and test it especially when marking "-dev" version manually.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is the cordova-coho command to use?
Where does one have to change things when doing this manually?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(Sorry about being pedantic here, but I guess you probably have this information handy)


## Before Release

### npm audit check
Expand Down