Well, I don't think adding the test without the fix is the right thing to
When we will try to make this test work, we will have totally forgotten
that there's a fix needed for that.
That's why I listed the commits we couldn't merge for now as we will have
to merge them later, once the feature has been implemented. And if you
merge the tests and the fix at once, at least you know what you're doing.
On Wed, Dec 19, 2018 at 7:21 PM Vlad Mihalcea <mihalcea.vlad(a)gmail.com>
We need the tests to be available to know whether 6.0 has regressions
5.x. Therefore, all the pending tests become the list of tasks to be
On Wed, 19 Dec 2018, 19:40 Guillaume Smet <guillaume.smet(a)gmail.com wrote:
> Hi Vlad,
> Not sure if it's better to partially push the commits or to have them in
> a list to deal with later (tests + commit).
> What do the others think about it?
> On Wed, Dec 19, 2018 at 6:37 PM Vlad Mihalcea <mihalcea.vlad(a)gmail.com>
>> I have merged some PRs and have some commits still left to integrate
>> into 6. Indeed that some if them cannot be fully integrated because they
>> rely on non-implemented functionality. But I'll add the tests in the
>> pending tests folder.
>> On Wed, 19 Dec 2018, 18:19 Guillaume Smet <guillaume.smet(a)gmail.com
>>> We had the first 5 -> 6 merge meeting with Chris yesterday. We
>>> cherry-picked all the simple things but there were a few more
>>> - things that needs to be ported soon but weren't a simple cherry-pick
>>> - things that cannot be ported right now because not yet available in 6
>>> We decided to push a document in the 6 tree containing the status so
>>> we have proper versioning:
>>> Andrea, Chris and Vlad each have one issue affected. Maybe let's try to
>>> target the next meeting as the limit for merging them (or push them to
>>> for later), probably January 8th-9th.
>>> When you're done with a merge, please remove the related content from
>>> document so that we can keep track of things.
>>> hibernate-dev mailing list