El 26.07.2017 a las 21:41, Richard Heck escribió:
Mike makes a good point. He wants to help with testing and improving the
documentation but cannot because of the file format. What is our policy
on updating the file format? I believe we only do that when we have to
update the format because we are using a new feature. Is that right?
Yes, as best we can. But in practice, the people updating the docs are
using the latest version, and the version number gets updated. (I think
this is why it's often suggested that updates be made in stable first,
not in master.)
Yes, that is why I write so often to put all changes to the
documentation that don't require a fileformat change to the stable
branch. This way everybody can have a look and review it.
I try to look at these changes soon and distribute the changes to the
different language files and port the changes to master. In the past I
got this way feedback from our translators so that I could correct it
for the next stable release. if it would have been only in master the
stable branch and thus the majority of users would not benefit from doc
corrections/updates.
My personal policy is to stop working on the stable branch docs with the
release of the first beta of a new version. This is just to save
manpower. We have not released a beta yet, but I already started the doc
updating for 2.3. So unless there is a compilation failure I would not
backport info to the 2.2 branch anymore.
regards Uwe
