Hi Peter,
Thanks for reminding the nuances. It's been a while since I contributed to
the codebase.
Ok, then I think nobody will object that the docs will always be published
from a release branch such as ignite-2.9.1 and then we can commit to the
branch directly if 2.9.1 needs to be updated.
Hi, Denis.
Apache Ignite as other projects on Apache is in fact released from TAG, not
BRANCH (although they are similar at that point).
Thus — it seems that there should be no problem to continue using branch as
docs sources for the same release as long as TAG stays intact.
We just have to
Igniters,
After we release a version, we create a docs-specific branch out of the
release branch for inevitable documentation improvements (feedback; generic
changes that are committed to the master, and the last published version).
For instance, once 2.9 was released from the "ignite-2.9"
