I don't think anyone mentioned expecting you to do this. In fact the
discussions I have had about this was that others would help with this
(after 5.2.13).
On Wed, Jan 24, 2018 at 5:20 PM Gail Badner wrote:
> People seem to be relying on me to backport to 5.2. From a product
> standpoint, ther
On Thu, Jan 25, 2018 at 9:22 AM Guillaume Smet
wrote:
> On Thu, Jan 25, 2018 at 3:55 PM, Steve Ebersole
> wrote:
>
>> And btw... the release announcement emails, tweets, forum posts, etc have
>> been simple links back to the blog post for YEARS. So not sure what you
>> mean about that happening
I don't know how applicable this is to the Hibernate project, but a
workflow I've seen is you do the fixes in the old maintenance-only branches
(say 5.1) and then merge or cherry-pick those changes into the
current-release branch. Of course if they've diverged too drastically in
very few commits, t
On Thu, Jan 25, 2018 at 3:55 PM, Steve Ebersole wrote:
> And btw... the release announcement emails, tweets, forum posts, etc have
> been simple links back to the blog post for YEARS. So not sure what you
> mean about that happening "lately".
>
I'm talking about the blog post itself.
I mean th
On Wed, Jan 10, 2018 at 5:41 AM Guillaume Smet
wrote:
> AFAICS, lately, the ORM bugfix releases announcement is just a link to the
> changelog. I don't think it would buy you a lot to automate it.
>
Its been a long time since I've personally done a ORM bugfix release. But
AFAIK we still do do a
