Personally I also think that we should refer people to Jira for this
information. We already have an authoritative version of this list (Jira)
and I generally dislike duplication.
But I am just trying to manage different perspectives. A few people raised
points that relying on Jira might not be the best for a few reasons. So
trying to reach a consensus that works for everyone.
I just know that an ~ 400Kb text file for this purpose is a bit of overkill
no matter what side of the fence people fall :)
On Wed, May 27, 2015 at 9:01 PM, Brett Meyer <brmeyer(a)redhat.com> wrote:
+1 from me. Although, on the other hand, do we really need to keep
maintaining that to begin with? I guess I never thought simply having
users go to the JIRA release notes was a big deal. Just my $.02.
----- Original Message -----
> From: "Steve Ebersole" <steve(a)hibernate.org>
> To: "Brett Meyer" <brmeyer(a)redhat.com>
> Cc: "Hibernate" <hibernate-dev(a)lists.jboss.org>, "Sanne
Grinovero" <
sanne(a)hibernate.org>
> Sent: Wednesday, May 27, 2015 9:57:39 PM
> Subject: Re: [hibernate-dev] Changelog file in Hibernate ORM
>
>
https://hibernate.atlassian.net/browse/HHH-9827
>
> On Wed, May 27, 2015 at 8:56 PM, Steve Ebersole <steve(a)hibernate.org>
wrote:
>
> > If I may dig up a zombie thread.. :)
> >
> > What I plan to do unless I hear loud arguments to the contrary is to
> > truncate this to just the current major release indicated by branch.
E.g.
> > the 4.2 branch would maintain changes just for 4.2 release family, etc.
> > This kind of goes hand-on-hand with what I am planning for the in-line
> > migration guide too.
> >
> > On Mon, Mar 4, 2013 at 10:40 AM, Steve Ebersole <steve(a)hibernate.org>
> > wrote:
> >
> >> Depends what you mean "sync it in master". Its not like you
should be
> >> cherry-picking changelog changes from other branches to master.
> >>
> >> But, you should be collecting the changes from Jira putting them into
the
> >> changelog on the indicated branch(es). Currently, that means anything
> >> marked jpa21 should get copied into the master changelog. Sames was
true
> >> for 4.2 before 4.2 was branched off, and 4.1 before that and so on.
> >> Granted it is more difficult in an environment like we have where we
> >> maintain multiple branches simultaneously. But this highlights the
> >> importance of marking versions correctly in Jira.
> >>
> >>
> >>
> >> On 03/04/2013 08:34 AM, Brett Meyer wrote:
> >>
> >>> I always maintain it in the 4.1/4.2 branches, but we admittedly
forget
> >>> to sync it in master. Up to you guys.
> >>>
> >>> Brett Meyer
> >>> Red Hat Software Engineer, Hibernate
> >>> +1 260.349.5732
> >>>
> >>> ----- Original Message -----
> >>> From: "Steve Ebersole" <steve(a)hibernate.org>
> >>> To: "Sanne Grinovero" <sanne(a)hibernate.org>
> >>> Cc: "Hibernate" <hibernate-dev(a)lists.jboss.org>
> >>> Sent: Sunday, March 3, 2013 10:42:12 AM
> >>> Subject: Re: [hibernate-dev] Changelog file in Hibernate ORM
> >>>
> >>> If I had to guess, Brett probably just missed updating that during
the
> >>> last few releases. I am open to discuss either option here; either
> >>> remove the file or maintain it.
> >>>
> >>>
> >>> On Sat 02 Mar 2013 02:58:56 PM CST, Sanne Grinovero wrote:
> >>>
> >>>> On 2 March 2013 20:51, Hardy Ferentschik
<hardy(a)hibernate.org>
wrote:
> >>>>
> >>>>> On 2 Mar 2013, at 21:19, Sanne Grinovero
<sanne(a)hibernate.org>
wrote:
> >>>>>
> >>>>> The file changelog.txt in the root ot the Hibernate ORM
project
> >>>>>> seems outdated.
> >>>>>>
> >>>>>
> >>>>> Personally I find this file useless. I think a link a link in
the
> >>>>> readme to the Jira changeling would suffice. However, I know
some
> >>>>> people think the changelog is valuable.
> >>>>>
> >>>>> But of course, it either needs to be maintained or deleted.
> >>>>>
> >>>>
> >>>> +1
> >>>> I'd prefer maintained, but otherwise deleted woudl be better
than
> >>>> misleading indeed.
> >>>>
> >>>> The reason I like it is that it allows me a very quick search on
the
> >>>> history of the current branch, while from JIRA it's not
immediate.
> >>>> Of course from there I continue on JIRA or GIT logs for more
insight..
> >>>>
> >>>> In this case I wanted to double-check if we had dropped OSCache
> >>>> support. I remember we had planned for it, but couldn't find
tracking
> >>>> about its removal in JIRA.
> >>>>
> >>>> Sanne
> >>>>
> >>>>
> >>>>>
> >>>>>>
> >>>>> --hardy
> >>>>>
> >>>> _______________________________________________
> >>>> hibernate-dev mailing list
> >>>> hibernate-dev(a)lists.jboss.org
> >>>>
https://lists.jboss.org/mailman/listinfo/hibernate-dev
> >>>>
> >>> _______________________________________________
> >>> hibernate-dev mailing list
> >>> hibernate-dev(a)lists.jboss.org
> >>>
https://lists.jboss.org/mailman/listinfo/hibernate-dev
> >>>
> >>
> >>
> >
>