Re: [hibernate-dev] "Stale" Hibernate issues
Hi Martijn, I'm CC'ing the mailing list -- there are a few misconceptions I'd
like to clear up for everyone.
First and foremost, statements like "But nobody from the Hibernate has ever taken a
look" are frankly frustrating. Hibernate is an open source project, not a
proprietary product with separated groups of consumers and producers. We all have our own
interests and priorities. If HHH-3930 is important for someone, pull requests or patches
would be fantastic and much appreciated by the community!
Your point argues against itself. There are so many issues that deserve the
community's attention, and HHH-3930 is no different from the rest. But due to the
sheer amount of open tickets, it was getting impossible to sort through them all. We have
to do *something* to narrow it down, and this was the best solution we could find.
Everyone, please keep in mind that if an issue is still valid on ORM 4, simply say so in a
comment. I'm more than happy to re-open them on a case-by-case basis. An aggressive
approach was necessary -- simply letting thousands of tickets sit there is, imho, much
worse.
Regarding the development of test cases, we've said from the beginning that, although
we certainly prefer runnable cases (either standalone or extending an existing unit test),
I've always thought that enough detail in the description (entities, mappings,
applicable settings, and code snippets) were perfectly acceptable and definitely making a
big attempt at helping out. That hasn't changed. However, several people have
mentioned wishing for a template project to use in creating standalone reproducers --
that's a great idea. I'm planning on putting one together soon and will share
it.
Brett Meyer
Red Hat, Hibernate ORM
----- Original Message -----
From: "Martijn Dashorst" <martijn.dashorst(a)gmail.com>
To: brmeyer(a)redhat.com
Sent: Monday, April 7, 2014 2:41:20 PM
Subject: "Stale" Hibernate issues
Dear Brett,
I understand the necessity of sorting out stale issues in a large project
as Hibernate, but blindly shafting folks that are waiting 5 years for a
proper response from the hibernate team is not the way to go.
Case in point: HHH-3930 has been open for 5 years, has provided a clear
description and code for two entities afflicted entities. But nobody from
the Hibernate has ever taken a look and commented on it for specific
information.
Only canned responses from mass updates have been provided.
I urge you to actually look at this issue and give proper feedback on what
is needed for it to be considered.
If the information is incomplete, or the report unclear, say so.
IMO you can only require folks adding a test case if you have a decent
guide of how to write one. Provide a maven archetype for it.
Requiring folks to have to checkout the hibernate project, figure out the
coding guidelines, having to peruse the test cases to figure out what to do
is really stretching it.
You state that you don't want to come across as arrogant, but from my
standpoint, the current actions actually make me wish I never had filed the
issue and just work around it, polluting my model and never going to file a
bug report with Hibernate ever again.
Martijn