Hi all, I just created a 5.5 branch on github for Hibernate Search, to backport (so far) one issue which you all had flagged as "fixed for 5.5.1" on JIRA: please always make sure the state of JIRA tracks the repository state accurately. Thanks, Sanne _______________________________________________ hibernate-dev mailing list hibernate-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev

ok I don't disagree with that idea - in fact that's what we normally do - but in that case I wouldn't have set the version to 5.6.0-SNAPSHOT yet, I was just confused by that On 30 September 2015 at 13:48, Gunnar Morling <gunnar(a)hibernate.org&gt; wrote: > Well, so far that issue was and is the only issue fixed after the > 5.5.0 release, so there is no need for branching until there are > commits 5.5.x commits to be integrated and commits meant for 5.6 only > already have been merged. I'd rather avoid working on several releases > in parallel as far as possible. > > 2015-09-29 11:58 GMT+02:00 Sanne Grinovero <sanne(a)hibernate.org&gt;: >> Hi all, >> I just created a 5.5 branch on github for Hibernate Search, to >> backport (so far) one issue which you all had flagged as "fixed for >> 5.5.1" on JIRA: please always make sure the state of JIRA tracks the >> repository state accurately. >> >> Thanks, >> Sanne >> _______________________________________________ >> hibernate-dev mailing list >> hibernate-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/hibernate-dev