Hello, so far, when a new major release a new branch was created with the first version in that branch: rel_1_0_0 - was for 1.0.x rel_1_1_0 - was for 1.1.x Some complained that it is not suggestive when minor release in the branch was done, like 1.0.1 or 1.1.1. So, let's try to find a way more convenient. So we will have release a.b.c, where c can be incremented several time, being like a patch update release for a.b.0. Proposed options: 1) a_b_0 - stick to current module 2) a_b_x - use x to signal that it is a changing number for same major release 3) a_b - ignore patch release number Other suggestions are welcome. Please feedback as soon as possible. The branch will be created in few hours. Cheers, Daniel