Re: [hibernate-dev] ORM 6 branch
I think it would be better to at least move the code to a 6.0 branch on the
main repository, just so that the code is a little easier to find for
external contributors/users. Even if it's named "6.0-wip" to mention that
you may end up rewriting history on that branch. If we release binaries,
then the code is official and should be in plain sight.
But if it's not an option, just pushing the 6.0.0.Alpha1 tag to the main
repository would be a step in the right direction.
Yoann Rodière
Hibernate NoORM Team
yoann(a)hibernate.org
On Tue, 27 Nov 2018 at 00:25, Sanne Grinovero <sanne(a)hibernate.org> wrote:
On Mon, 26 Nov 2018, 23:39 Gail Badner <gbadner(a)redhat.com wrote:
> That's fine with me.
>
+1 But could you push the release tag to the reference repo? Just to make
sure we have it for future reference.
Thanks
> On Mon, Nov 26, 2018 at 11:29 AM Steve Ebersole <steve(a)hibernate.org>
> wrote:
>
> > This Wednesday we plan to release 6.0 Alpha1 and I thought it best to
> start
> > discussing how to best handle the 6.0 and master branches.
> >
> > I think we should keep 6.0 a little while longer in my fork and 5.4 as
> > master until 6.0 becomes more stabilized to make it easier for 5.4
> > maintenance. And reconsider as we approach Beta1.
> >
> > But this affects everyone, so wanted to see what others thought...
> > _______________________________________________
> > hibernate-dev mailing list
> > hibernate-dev(a)lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/hibernate-dev
> >
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev