Yes and no. The issues are closed *against 6.0*, which is still
technically correct for the current state. The changes are still
integrated into the metamodel branch which correlates to 6.0 in jira.
The question is more *which* of those changes we want to migrate to master.
On Wed, Dec 3, 2014 at 6:30 AM, Sanne Grinovero <sanne(a)hibernate.org> wrote:
Don't you all think it's very troubling that several issues
in JIRA
are marked as "resolved" but are not actually integrated in the new
master?
This query is probably not perfect but I hope it's enough to highlight
the problem:
https://hibernate.atlassian.net/issues/?filter=15161&jql=project%20%3...
On 1 December 2014 at 23:31, Steve Ebersole <steve(a)hibernate.org> wrote:
> I am finishing up the initial 5.0 work for master right now. I will work
> on these next. Ping me at the end of the week so I dont forget :)
>
> On Mon, Dec 1, 2014 at 3:07 PM, Andrej Golovnin <golovnin(a)gmx.net>
wrote:
>
>>
>> > They should get moved to the 4.3-based master. I think I found the
>> relevant issues:
>> >
>> > * Oracle12cDialect -
https://hibernate.atlassian.net/browse/HHH-9044
>> > * PostgreSQL92Dialect & PostgreSQL94Dialect -
>>
https://hibernate.atlassian.net/browse/HHH-9167
>> >
>> > I have reopened them and targeted them for 5.0
>>
>> Do you already know when they will get moved to the 4.3-based master?
>> I think I should wait with my pull request until they get moved.
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/hibernate-dev