+1 I agree that the versioning pattern should be changed and that `<cli version>-<year>.<month>` would likely be the best pattern to use.
On Tue, Jul 30, 2024 at 5:24 AM Norman Breau <nor...@breautek.com> wrote: > It's been awhile since I last did a snapshot so I kinda forget what the > process is > but it might involve some tool changes inside tools/bin > > On 2024-07-29 16:14, Niklas Merz wrote: > > +1 from me > > > > I think this is a good idea because you can see easily if you are > > looking at the latest docs. > > > > How would those snapshots with timestamps work? Do they happen > > automatically with a GitHub action or manually once we release something > > significant? > > > > On July 26, 2024, Norman Breau <nor...@breautek.com> wrote: > >> Hi Team, > >> > >> I've been giving docs some love, due to it missing some important > >> documentation for cordova-android@13. > >> > >> Historically we released a snapshot of the docs when we released a > >> new > >> CLI version, and a new CLI version is often associated with some > >> default > >> fixed platform versions. > >> > >> Now-a-days the CLI version is not as significant because by default > >> they > >> will install the latest version of the platform unless specified > >> otherwise, and we are finding less of a need to make new releases of > >> the > >> CLI I think, while iOS & Android still sees regular releases, usually > >> a > >> major release per year. > >> > >> I've chatted in private with some people and we had the idea that > >> perhaps moving forward we can snapshot the docs version using a > >> format > >> of `<cli version>-<year>.<month>`. If for example, I were to snapshot > >> the docs today, the doc version might look like `12.x-2024.07`. > >> > >> Anything already existing will remain as is. We will not retro change > >> all the current snapshots. > >> > >> Just wondering if anybody else any opinions, thoughts, or objections > >> as > >> I may be looking into doing a snapshot of the docs soon. > >> > >> Cheers, > >> Norman > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > >> For additional commands, e-mail: dev-h...@cordova.apache.org > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org > >
