breautek commented on issue #1432: URL: https://github.com/apache/cordova-docs/issues/1432#issuecomment-3568309220
> Should cordova-android 14 not also added to the cordova-cli 12 docs? It really should be. > [@GitToTheHub](https://github.com/GitToTheHub) That's a fair question. I added Android 14 to the 12.x docs because: > > 1. cordova-android 14 has been released and is available for use > > 2. Users need documentation for the currently available platform version > > 3. The dev docs already have it - it just wasn't propagated to stable docs > > 4. Backward compatibility - CLI 12.x can use cordova-android 14.x > > > If there's a release process where platform docs should only be updated with CLI releases, please let me know the correct approach. I want to make sure this follows the project's documentation practices. There's been recent improvements on this process... and as a result it means I'm no longer familiar but I believe there is a gulp or maybe a `npm run` script that does a "snapshot", which basically makes a <cli-version>-<date> release and copies everything from dev and places it into that version. https://github.com/apache/cordova-docs/blob/master/doc/working-on-docs.md is the relevant docs on how to build a snapshot/release. I **think** you can do this in a branch to create a pull request. There are several ways to build a new release: ``` npm run update-docs ``` which sounds like it just updates the latest version. That may be satisfactory but idk if there are any other changes that warrants a timestamp update, which leads to the second path: ``` npx gulp newversion ``` which I believe just creates a new 12.x-<timestamp> release which I believe is okay to do in this situation. I glanced over recent [commits](https://github.com/apache/cordova-docs/commits/master/) and I don't see anything that I think would prevent us creating a new `12.x` snapshot. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
