Fixed the branch alias for master

[stof]

No description provided.

[ruflin]

@stof Can you update the changes.txt file?

[stof]

is it really worth it ? this is just something which should have been part of the release process actually (master already contains the 1.3.x codebase before my change, not the 1.2.x one)

[ruflin]

Yes, I think it is worth to mention as you rightly said, that it is not part of the release process yet. Probably this should be added here: http://elastica.io/release/how-to-create-an-elastica-release.html

[stof]

I updated it

[fprochazka]

@ruflin you know.. if there is going to be every insignificant change in the file, than you're basically recreating commit log and having more noise than useful informations in the changes.txt... changelog is for changes that are relevant if you're updating the lib, like "added method, added feature, bc break, ..." not noise like typo and release process details.

Just saying.

[ruflin]

@fprochazka My view on this:

• Every pull request should be related to an issue. Every issue is hopefully relevant.
• Every pull request consists of several commits.
• Every issue / pull request should have a self explanatory title
• The changelog should be generated of the issues with the titles (automated).

We are definitively missing the last points which would make to change the changes.txt file manually obsolete. That is where the project should be heading.

[Tobion]

So if there is a PR to fix typos. This will be part of the changelog. I agree this is too much noise.

[ruflin]

I fully agree on documentation typos.