[hibernate-dev] Branching strategy in OGM

Sanne Grinovero sanne at hibernate.org
Thu Feb 26 09:16:33 EST 2015

Hey all,
it seems like the branch for maintenance work on OGM 4.1 is (still)
called "master", while a branch "4.2" was created for future work.

I'd really prefer it the other way around: create a branch "4.1" to
host all changes which are needed to be backported on 4.1.x , and call
"master" what will receive all of the latest improvements.

Let's see on IRC when it is a good time to rename the branches? It
better happens "atomically" or it's a mess..


More information about the hibernate-dev mailing list