Daniel-Constantin Mierla
2014-10-08 21:56:36 UTC
Hello,
short note to say that the branch 4.2 has been created, as announced on
mailing list a while ago.
This is the official branch to be used for releasing any of the 4.2.x
versions. The first one, v4.2.0, is expected to be out in about one week.
The version used now in master branch is prefixed with 4.3.0, which is
expected to be the next future major release. With this change,
practically commits with new features to be part of 4.3.0 can be pushed
to master branch from now on.
Any fix that is applicable for both master and 4.2 branches has to be
committed first in master branch, then cherry-picked or merged to branch
4.2.
Cheers,
Daniel
short note to say that the branch 4.2 has been created, as announced on
mailing list a while ago.
This is the official branch to be used for releasing any of the 4.2.x
versions. The first one, v4.2.0, is expected to be out in about one week.
The version used now in master branch is prefixed with 4.3.0, which is
expected to be the next future major release. With this change,
practically commits with new features to be part of 4.3.0 can be pushed
to master branch from now on.
Any fix that is applicable for both master and 4.2 branches has to be
committed first in master branch, then cherry-picked or merged to branch
4.2.
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda