There is not a hard date. Not in the immediate future is the best I can
say at the moment.
On Mon, May 30, 2022 at 3:54 AM Imre Jonk via hibernate-dev <
hibernate-dev@lists.jboss.org> wrote:
> Hi there,
>
> We're very excited about the Hibernate ORM 6.0 release! Our developers
> have looked at
On Mon, 2022-05-30 at 09:35 -0500, Steve Ebersole wrote:
> There is not a hard date. Not in the immediate future is the best
> I can say at the moment.
Thanks for your reply, Steve. It would be nice if 5.6 continues to
receive bugfixes for some time. That would allow us to further validate
our re
The reality is that we are a very small team - it is simply not feasible to
maintain that many branches[1].
You are not asking about "time to upgrade" anyway, in my opinion. You are
asking about removing the need to upgrade, which is very different. Us
stopping support for 5.6 does not mean you
Hi Steve, I have a feeling that there is a slight misunderstanding
here, for which I'm sorry. Please allow me to clarify some things.
On Tue, 2022-05-31 at 07:31 -0500, Steve Ebersole wrote:
> The reality is that we are a very small team - it is simply not
> feasible to maintain that many branches
On Tue, May 31, 2022 at 11:18 AM Imre Jonk via hibernate-dev <
hibernate-dev@lists.jboss.org> wrote:
>
> I think the reality is that people who use software that has been
> declared end-of-life by their suppliers often don't backport it
> themselves. I've unfortunately seen enough cases of this ha
Hi Steve,
Thanks for the kind reply, I'm glad we could clear things up a bit. I
felt quite bad about the miscommunication and have been blaming myself
for it.
On Tue, 2022-05-31 at 11:48 -0500, Steve Ebersole wrote:
> Before I was lucky enough to get paid for working on Hibernate, I
> worked on i
Happened to be doing my morning email purge and this luckily came in at
just that time :D
On Wed, Jun 1, 2022 at 7:32 AM Imre Jonk via hibernate-dev <
hibernate-dev@lists.jboss.org> wrote:
> Hi Steve,
> You can find our
> support policy here if you are interested:
> https://www.ciphermail.com/do
On Wed, 2022-06-01 at 08:21 -0500, Steve Ebersole wrote:
> > You can find our support policy here if you are interested:
> > https://www.ciphermail.com/documentation/faq/support-policy.html
>
> That seems very similar to the one I wrote for Hibernate. I do see
> now that ours is probably a bit un
I think we generally agree and understand each other here.
On Thu, Jun 2, 2022 at 6:32 AM Imre Jonk via hibernate-dev <
hibernate-dev@lists.jboss.org> wrote:
>
> This sounds a lot like how we do our version numbering as well. We try
> to be as backward-compatible as possible with new "y" (minor)
Let me know what y'all think -
https://github.com/hibernate/hibernate-orm/wiki/Huge-Project,-Small-Team
On Thu, Jun 2, 2022 at 7:37 AM Steve Ebersole wrote:
> I think we generally agree and understand each other here.
>
>
> On Thu, Jun 2, 2022 at 6:32 AM Imre Jonk via hibernate-dev <
> hibernate
Looks great, thanks for writing that up!
Am 02.06.2022 um 18:52 schrieb Steve Ebersole:
Let me know what y'all think -
https://github.com/hibernate/hibernate-orm/wiki/Huge-Project,-Small-Team
On Thu, Jun 2, 2022 at 7:37 AM Steve Ebersole wrote:
I think we generally agree and understand each
On Thu, 2022-06-02 at 07:37 -0500, Steve Ebersole wrote:
> > But in the end, given a large enough userbase, every
> > (documented or undocumented) behavior of an API is being relied
> > upon by someone, meaning that every change will break someone's
> > workflow: https://xkcd.com/1172/
>
> Extrapo
On Thu, 2022-06-02 at 11:52 -0500, Steve Ebersole wrote:
> Let me know what y'all think -
> https://github.com/hibernate/hibernate-orm/wiki/Huge-Project,-Small-Team
Looks really good! Like I said in my previous email, it is good to see
the public/private API distinction documented. The 'qualifier'
13 matches
Mail list logo
