[Development] Documentation typo fixes

[Edward Welbourne]

On 7 February 2017 at 08:39, Ch'Gans <chgans at gna.org> wrote:
>> It's been a while that I notice some typos here and there in Qt5
>> documentation (mainly qtbase), and i decided that i would start
>> correcting them in the source code.

Thank you :-)

[snip]
>> documentation looks always nicer without typos.

Indeed it does.

>> I would like to know to which branch should i target such "code
>> review" on gerrit.
>> Should it be "Current release", "Next release", "dev" or "master"?
>> My gut feeling tells me "dev", so that from there, maintainers can
>> decide if they want to propagate or not.
>> Could someone confirm this?

Sze Howe Koh (7 February 2017 04:35) replied:
> See http://wiki.qt.io/Branch_Guidelines (Note: Qt module repositories
> don't have a "master" branch)
>
> Right now, the branches that accept documentation fixes are:
>
> * 5.8 (stable branch)
> * 5.9 (next release branch)
> * dev (development branch)
>
> Simply put, patches will merge from the top of the list to the bottom
> of this list. For example, patches that go into "5.8" will eventually
> be merged into "5.9", which in turn will eventually be merged into
> "dev".
>
> Typo fixes are not new features or major/risky changes, so they can go
> into the stable branch ("5.8").

Indeed.  This is all being formalised in QUIP 5:
https://codereview.qt-project.org/178906
where you can find out all you wish to know about which changes should
go to which branches,

	Eddy.