The rename was applied now.
"master" is now referring to the branch which was previously called
The maintenance branch for 5.6.x is now named "5.6".
I will not delete the branch "5.7" branch, for convenience of the open
pull requests and any work in progress you might have. Let's make sure
any such change is merged to master first though, then "backported" as
usual.. eventually when we release it 5.7 will just be the maintenance
branch of 5.7.
On 23 January 2017 at 11:39, Sanne Grinovero <sanne(a)hibernate.org> wrote:
I'm soon going to rename branches on the reference repository
"master" branch is going to be renamed "5.6"
"5.7" branch is going to be renamed "master"
If you keep this in mind, you should be able to avoid any trouble:
rebase as usual before sending PRs, just make sure you updated your
local references to match the reference and then use the new names
during the rebase.
If you get in trouble.. I'm open to help out.
Reminder: with git what matters is the commit signature: "renaming"
just means we're moving the labels from one branch to the other; the
branch itself is not being affected.