|
7 | 7 | * This can also be executed via `gulpfile.js` task `fetch`, by running `gulp fetch` which pulls in the files to `dev/en/{file dest}`.
|
8 | 8 | * Most auto-generated files have a comment tag at the top of the file to indicate that they come from elsewhere.
|
9 | 9 |
|
10 |
| -## Update latest (x.y) from `dev` |
| 10 | +## Update current docs from `dev` |
11 | 11 |
|
12 |
| -Normal build doesn't update latest (7.x) from dev version of docs. You will need to do this manually using `gulp snapshot`. Read more [here](https://github.com/apache/cordova-docs/blob/master/gulpfile.js#L212). |
| 12 | +The following command can quickly sync the `dev` docs with the current latest docs: |
13 | 13 |
|
14 |
| -## Create new version of the docs |
| 14 | +```bash |
| 15 | +npm run update-docs |
| 16 | +``` |
15 | 17 |
|
16 |
| -To increment the documentation version (e.g. `X.X.X`, either use the gulp task: |
| 18 | +## Create new snapshot from `dev` |
17 | 19 |
|
18 |
| - gulp newversion --version X.X.X |
| 20 | +The following commands can be used to create a new snapshot of `dev` docs: |
19 | 21 |
|
20 |
| -or manually run the `incrementversion.js` script: |
| 22 | +```bash |
| 23 | +npx gulp newversion |
| 24 | +npx gulp newversion --bumpCli |
| 25 | +``` |
21 | 26 |
|
22 |
| - node ./tools/bin/incrementversion.js www/docs X.X.X |
| 27 | +Please read the section, [Preparing Doc Release Scenarios](#Preparing-Doc-Release-Scenarios), below to understand which command fits your scenario. |
23 | 28 |
|
24 |
| -To only run for a specific language (__this should only happen when translation is intentionally left out for a given version__), specify the language to the Gulp task as follows: |
| 29 | +## Preparing Doc Release Scenarios |
25 | 30 |
|
26 |
| - gulp newversion --version X.X.X --language YY |
| 31 | +When preparing to release docs, there are two things to be aware of, the version of Cordova CLI and if the changes warrants for a new doc version. |
27 | 32 |
|
28 |
| -or manually, to the script, as follows: |
| 33 | +Here are a few scenarios that will help decide how if we are updating an existing snapshot of creating a new one. |
29 | 34 |
|
30 |
| - node ./tools/bin/incrementversion.js www/docs X.X.X YY |
| 35 | +1. Are we preparing to release new docs because there was a major release of Cordova CLI? |
| 36 | + |
| 37 | + If the answer is **yes**, then we will be creating a new version of docs with the following command: |
| 38 | + |
| 39 | + ```bash |
| 40 | + npx gulp newversion --bumpCli |
| 41 | + ``` |
| 42 | + |
| 43 | + If the current released docs version is `12.x` and we are preparing for Cordova-CLI 13.x, the above command will create `13.x-2024.10`. |
| 44 | + |
| 45 | + > Notice: The year and month will be appended automatically. |
| 46 | + |
| 47 | +2. Are we preparing to release new docs because there was a minor or patch release of Cordova CLI? |
| 48 | + |
| 49 | + If the answer is **yes**, then we do not need to make a new snapshot. In this case, we can update an existing snapshot with the following command: |
| 50 | + |
| 51 | + ```bash |
| 52 | + npm run update-docs |
| 53 | + ``` |
| 54 | + |
| 55 | + > Notice: In this scenario we are expecting the version to already exist. If it was missing, then we would have to create a new snapshot but in most cases it should never be missing. |
| 56 | + |
| 57 | +3. Are we preparing docs for a major release to one or more of Cordova's platforms while the CLI version was unchanged? |
| 58 | +
|
| 59 | + If the answer is **yes**, then we need to make a new snapshot, but we do not need to bump the CLI major. We can do this with the following command: |
| 60 | +
|
| 61 | + ```bash |
| 62 | + npx gulp newversion |
| 63 | + ``` |
| 64 | +
|
| 65 | + If the current doc snapshot is `12.x`, then the above command will create a new snapshot with the same CLI major version but the appended date will be different. |
| 66 | +
|
| 67 | + E.g. `12.x-2024.10` |
| 68 | +
|
| 69 | + > Notice: |
| 70 | + > |
| 71 | + > *`12.x` and older does not have date appended. Any newly created snapshots will append the date value. |
| 72 | + > * If we already have `12.x-2024.10` and the month is still the same, we should use senario 2. `npm run update-docs`. |
0 commit comments