Re: [hibernate-dev] Master
Sounds reasonable. Do you think it will be unstable, i.e. should we
temporarily disable complaint emails from Jenkins, or even the full
build tasks?
Also, this implies that any future backport becomes similarly harder,
so you could also simply ask others to hold pushing on master, then
have people forward-port when it's done.. it's the same really but
that's why I mention it: as the complexity is interchangeable it's a
fair request, with the difference you have:
- others help you port the other patches forward rather than doing it all alone
- the authors of the original patch doing it, that should make it a bit simpler
On 6 April 2016 at 17:15, Steve Ebersole <steve(a)hibernate.org> wrote:
Obviously consolidating hibernate-entitymanager into hibernate-core
is a
fairly big effort. And I am getting concerned about the continuing pushes
to master in the meantime, many of which I know touch on code I have
changed. My concern is obviously getting done all this refactoring work
and then having to sift through all of the changes that have been pushed in
the interim and attempting to work out the proper integration strategy.
Long story short... I am contemplating pushing to master sooner rather than
later even though my refactoring may not be completely finished, especially
as we get towards the end of the week.
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev