Hi,
Just released 5.3.2 and created a 5.3 branch.
master is now 5.4 (it might be changed to 6.0 later if we don't make any
release until 6)
I'm going to setup proper CI for the 5.3 branch.
--
Guillaume
On Tue, Jul 3, 2018 at 6:55 PM Chris Cranford wrote:
> +1 from me as well.
>
> On 07/02/2
+1 from me as well.
On 07/02/2018 05:43 PM, andrea boriero wrote:
> +1 for 5.3 branch
>
> On Mon, 2 Jul 2018, 19:05 Gail Badner, wrote:
>
>> +1 on creating a 5.3 branch, with master being used for 5.4 (or 6.0).
>>
>> On Mon, Jul 2, 2018 at 9:43 AM, Sanne Grinovero
>> wrote:
>>
>>> On Mon, 2 Jul
+1 for 5.3 branch
On Mon, 2 Jul 2018, 19:05 Gail Badner, wrote:
> +1 on creating a 5.3 branch, with master being used for 5.4 (or 6.0).
>
> On Mon, Jul 2, 2018 at 9:43 AM, Sanne Grinovero
> wrote:
>
> > On Mon, 2 Jul 2018 at 17:34, Steve Ebersole wrote:
> > >
> > > I don't mind creating a 5.3
+1 on creating a 5.3 branch, with master being used for 5.4 (or 6.0).
On Mon, Jul 2, 2018 at 9:43 AM, Sanne Grinovero wrote:
> On Mon, 2 Jul 2018 at 17:34, Steve Ebersole wrote:
> >
> > I don't mind creating a 5.3 branch, and having master for "after 5.3"
> development with 6.0 hopefully merged
On Mon, 2 Jul 2018 at 17:34, Steve Ebersole wrote:
>
> I don't mind creating a 5.3 branch, and having master for "after 5.3"
> development with 6.0 hopefully merged in there soon.
+1 that sounds like the best option we have. It's not extremely
urgent, we can do this after 5.3.2 ?
Just making su
I don't mind creating a 5.3 branch, and having master for "after 5.3"
development with 6.0 hopefully merged in there soon.
On Mon, Jul 2, 2018 at 11:23 AM Steve Ebersole wrote:
> I think I have pointed out before that such a schedule is already posted :
> https://github.com/sebersole/hibernate-c
I think I have pointed out before that such a schedule is already posted :
https://github.com/sebersole/hibernate-core/blob/wip/6.0/design/6.0-todo.adoc#alpha1
The important part remaining is really collection support.
There are a few listed there that we'd be willing to push to the next Alpha
O
Hi Sanne,
On Mon, Jul 2, 2018 at 5:48 PM Sanne Grinovero wrote:
> Not sure what to suggest to people wanting to contribute new features
> today; maybe hold as we assume the 6.0 work will be merged in master
> soon? Will be hard to say no to many reasonable requests though.
>
IMHO, there are 2 t
If 5.3 cannot take new features, it's better to branch it and have a 5.4
branch for the master until 6.0 is ready.
There are lots of interesting improvements that are provided via PRs or as
suggestions on the forum, so it would be detrimental to our users to delay
those until 6.0 can be used in p
