[hibernate-dev] Only blockers should be fixed in Hibernate ORM 5.0 branch

[Gunnar Morling]

Stupid question probably: Why do we maintain 5.0.x at all, now that
5.1.0.Final is out? Is it that EAP or WF will continue to be using
5.0.x? If so, why is that, couldn't they move to 5.1?

2016-03-17 22:17 GMT+01:00 Sanne Grinovero <sanne at hibernate.org>:
> On 17 March 2016 at 17:40, Steve Ebersole <steve at hibernate.org> wrote:
>> To be honest, I think its best if we somehow notify you for issues fixed
>> that we think should be considered for inclusion on 5.0 branch and you can
>> decide.  A label or a filter.  Something like that
>
>
> +1 Shouldn't any bug be considered? Even if it's not a blocker but
> it's annoying ..
>
> Personally I'd use a JIRA filter based on the "affects" field and
> type=bug; if any you might want a label to exclude them from this list
> so you don't have to review an ever-growing list.
>
> -- Sanne
>
>>
>> On Wed, Mar 16, 2016 at 5:30 PM Gail Badner <gbadner at redhat.com> wrote:
>>
>>> Please do not backport any fixes that are not blockers. If you are not sure
>>> if an issue is a blocker, then please ask before pushing to 5.0.
>>>
>>> Thanks,
>>> Gail
>>> _______________________________________________
>>> hibernate-dev mailing list
>>> hibernate-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>>
>> _______________________________________________
>> hibernate-dev mailing list
>> hibernate-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev