I do like the idea of having past documentation available, but I'm not sure I see how this would work. What if there are updates to the site that need to be made that are independent of a particular release (e.g. adding a commiter)? Would I go back and edit the previous release branch? Do we somehow label parts of the site as being release-independent? Even if this is the case, consider when we might have to correct documentation errors from a revious release. There may well be a path forward to make this work, but it's not obvious to me at the moment. -- Michael Mior [email protected]
Le dim. 8 déc. 2019 à 15:53, Vladimir Sitnikov <[email protected]> a écrit : > > >There are changes > >such as documentation for new features, etc that should not be published > >immediately > > Could we publish "master" documentation under /master or /nightly folders? > Anyway, it makes sense to publish multiple versions of the documentation. > > So why don't we publish master documentation as well? > > For instance: > https://docs.gradle.org/nightly/userguide/userguide.html > https://docs.gradle.org/6.0.1/userguide/userguide.html > https://docs.gradle.org/5.6.4/userguide/userguide.html > > And so on. > > I suggest we drop "site" branch, and build the site from "master + release > branches (or tags) for the past releases". > Then the site update would be as follows: > - commit to master > - done > > Vladimir
