[hibernate-dev] Changelog file in Hibernate ORM

[Steve Ebersole]

I am only planning to truncate this moving forward.  In fact it is already
done in master, aside from adding notes about where the 5.0 changes
dovetail with 4.3 changes.

On Fri, May 29, 2015 at 12:43 PM, Gail Badner <gbadner at redhat.com> wrote:

> I would prefer retaining all bugs fixes that feed into EAP.
>
> The first Hibernate version used by EAP was roughly 3.2.4.sp1 (there were
> a few extra commits included in the version that got into EAP).
>
> Are you planning to truncate the change logs for 3.2 or 3.3? If so, it
> would be helpful to me retain the bug fixes in those changelogs going back
> to at least 3.2.4.sp1
>
> FWIW, I'm fine with the changelog containing everything. I don't
> particularly care how large they get.
>
> ----- Original Message -----
> > From: "andrea boriero" <dreborier at gmail.com>
> > To: "Sanne Grinovero" <sanne at hibernate.org>
> > Cc: "Hibernate Dev" <hibernate-dev at lists.jboss.org>
> > Sent: Friday, May 29, 2015 4:48:08 AM
> > Subject: Re: [hibernate-dev] Changelog file in Hibernate ORM
> >
> > I would mantain all 5.x in the same changelog file and may be the
> previous
> > one.
> >
> > On 29 May 2015 at 12:32, Sanne Grinovero <sanne at hibernate.org> wrote:
> >
> > > I wouldn't stay awake at night because of that :) maybe only if the
> > > file gets huge?
> > > It's useful for people migrating, but since I doubt someone would
> > > migrate from pre-1.0 (at least without expecting to rewrite it all),
> > > that's why I suggested to keep from 3.0 onwards.
> > >
> > > On 29 May 2015 at 12:16, Steve Ebersole <steve at hibernate.org> wrote:
> > > > So it makes sense to you that the changelog for 5.0 includes entries
> for
> > > pre
> > > > 1.0?
> > > >
> > > > On Fri, May 29, 2015 at 6:09 AM, Sanne Grinovero <
> sanne at hibernate.org>
> > > > wrote:
> > > >>
> > > >> I'm +1 especially to keep the changelog.txt file both maintained and
> > > >> included.
> > > >>
> > > >> About pruning older content: I'd keep the past few years at least,
> for
> > > >> sake of who's finally upgrading.
> > > >> Maybe since version 3.0 onwards? Or just keep it all :)
> > > >>
> > > >> On 29 May 2015 at 12:05, Steve Ebersole <steve at hibernate.org>
> wrote:
> > > >> > I'm really not sure what y'all are +1'ing Emmanuel and Sanne.  You
> > > want
> > > >> > to
> > > >> > keep a massive changelog.txt containing all history forever?
> > > >> >
> > > >> > On Fri, May 29, 2015 at 5:59 AM, Sanne Grinovero <
> sanne at hibernate.org
> > > >
> > > >> > wrote:
> > > >> >>
> > > >> >> On 29 May 2015 at 08:15, Emmanuel Bernard <
> emmanuel at hibernate.org>
> > > >> >> wrote:
> > > >> >> >
> > > >> >> >> On 28 May 2015, at 10:42, Hardy Ferentschik <
> hardy at hibernate.org>
> > > >> >> >> wrote:
> > > >> >> >>
> > > >> >> >> On Wed, May 27, 2015 at 10:01:51PM -0400, Brett Meyer 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.
> > > >> >> >>
> > > >> >> >> Same for me on both counts, the proposed handling of
> changelog.txt
> > > >> >> >> as
> > > >> >> >> well as Brett's comment regarding the usefulness of this file
> > > >> >> >> altogether.
> > > >> >> >
> > > >> >> > A more frequent than I thought usage of changelog vs JIRA is a
> mix
> > > of
> > > >> >> > Ctrl+F + quick scan to know what has changed in a library or
> know
> > > >> >> > what is
> > > >> >> > affecting me. JIRA is not the most intuitive UI in the
> universe.
> > > With
> > > >> >> > allt
> > > >> >> > he bug statuses, the various intermediary releases to select
> etc,
> > > >> >> > nothing
> > > >> >> > beats changelog.txt.
> > > >> >>
> > > >> >> +1
> > > >> >> - JIRA's UI is not too bad but let's remember that while we use
> it
> > > >> >> since years, others might not feel comfortable with it
> > > >> >> - many of those receiving our "dist" package might not have
> internet
> > > >> >> access at all
> > > >> >> - the dist packages is long term archived, like we include
> sources it
> > > >> >> should contain a snapshot of all state. I like JIRA but who
> knows how
> > > >> >> long it will be there?
> > > >> >>
> > > >> >> _______________________________________________
> > > >> >> 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
> > >
> > _______________________________________________
> > 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
>