The file changelog.txt in the root ot the Hibernate ORM project seems outdated.

On 2 March 2013 20:51, Hardy Ferentschik <hardy(a)hibernate.org&gt; wrote: > > On 2 Mar 2013, at 21:19, Sanne Grinovero <sanne(a)hibernate.org&gt; 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

On 3 March 2013 15:42, Steve Ebersole <steve(a)hibernate.org&gt; wrote: > 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. I'd vote to maintain it. Not everyone is familiar with JIRA, and it's nice to include in the distributions. > > > > 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&gt; wrote: >>> >>> >>> On 2 Mar 2013, at 21:19, Sanne Grinovero <sanne(a)hibernate.org&gt; 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

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&gt; To: "Sanne Grinovero" <sanne(a)hibernate.org&gt; Cc: "Hibernate" <hibernate-dev(a)lists.jboss.org&gt; 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&gt; wrote: >> >> On 2 Mar 2013, at 21:19, Sanne Grinovero <sanne(a)hibernate.org&gt; 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 _______________________________________________ hibernate-dev mailing list hibernate-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev

I'd vote for continuing to maintain it as well. But I wonder if we ought to start truncating the back side of it. 10+ years is an awful lot of release/fix history and I doubt anyone seriously cares about about more that 5 years back (or less). Or maybe partitioned changelog files (1.0 versus 2.0 versus 3.0 versus...) On Mon 04 Mar 2013 08:34:10 AM CST, 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&gt; > To: "Sanne Grinovero" <sanne(a)hibernate.org&gt; > Cc: "Hibernate" <hibernate-dev(a)lists.jboss.org&gt; > 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&gt; wrote: >>> >>> On 2 Mar 2013, at 21:19, Sanne Grinovero <sanne(a)hibernate.org&gt; 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 _______________________________________________ hibernate-dev mailing list hibernate-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev

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&gt; > To: "Sanne Grinovero" <sanne(a)hibernate.org&gt; > Cc: "Hibernate" <hibernate-dev(a)lists.jboss.org&gt; > 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&gt; wrote: >> >>> On 2 Mar 2013, at 21:19, Sanne Grinovero <sanne(a)hibernate.org&gt; 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 >

From: "Steve Ebersole" <steve(a)hibernate.org&gt; To: "Brett Meyer" <brmeyer(a)redhat.com&gt; Cc: "Hibernate" <hibernate-dev(a)lists.jboss.org&gt;, "Sanne Grinovero" <sanne(a)hibernate.org&gt; 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&gt; 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&gt; > 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&gt; >>> To: "Sanne Grinovero" <sanne(a)hibernate.org&gt; >>> Cc: "Hibernate" <hibernate-dev(a)lists.jboss.org&gt; >>> 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&gt; wrote: >>>> >>>>> On 2 Mar 2013, at 21:19, Sanne Grinovero <sanne(a)hibernate.org&gt; 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 >>> >> >> >

+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.

Here is my 2 cents. I find it helpful that the changelog contains all jiras for all releases that feed into a particular version. It makes it clear when later branches were branched off. This is particularly helpful when we are maintaining multiple branches and commits are being backported to different branches. My preference would be to truncate the changelogs to the point at which 4.2, 4.3, and 5 branches diverge. For master: include everything starting form 4.3.6.Final (the last version in master changelog that is also included in 4.3 changelog). For 4.3: include everything starting from 4.1.5.SP1 (the last version in 4.3 changelog that is also included in 4.2 changelog). For 4.2: leave changelog.txt as is. This helps me track down when things are amiss (e.g., for regressions). I know there are other ways to investigate things related to misplaced/forgotten commits, but the changelogs have been a good starting point for me. Gail ----- Original Message ----- > From: "Hardy Ferentschik" <hardy(a)hibernate.org&gt; > To: "Brett Meyer" <brmeyer(a)redhat.com&gt; > Cc: "Hibernate" <hibernate-dev(a)lists.jboss.org&gt; > Sent: Thursday, May 28, 2015 1:42:05 AM > Subject: Re: [hibernate-dev] Changelog file in Hibernate ORM > > 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. > > --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

On 28 May 2015, at 10:42, Hardy Ferentschik <hardy(a)hibernate.org&gt; 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.

On 29 May 2015 at 08:15, Emmanuel Bernard <emmanuel(a)hibernate.org&gt; wrote: > >> On 28 May 2015, at 10:42, Hardy Ferentschik <hardy(a)hibernate.org&gt; 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(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev

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(a)hibernate.org&gt; 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(a)hibernate.org&gt; > wrote: >> >> On 29 May 2015 at 08:15, Emmanuel Bernard <emmanuel(a)hibernate.org&gt; wrote: >> > >> >> On 28 May 2015, at 10:42, Hardy Ferentschik <hardy(a)hibernate.org&gt; >> >> 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(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

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(a)hibernate.org&gt; 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(a)hibernate.org&gt; > 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(a)hibernate.org&gt; 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(a)hibernate.org > >> > wrote: >> >> >> >> On 29 May 2015 at 08:15, Emmanuel Bernard <emmanuel(a)hibernate.org&gt; >> >> wrote: >> >> > >> >> >> On 28 May 2015, at 10:42, Hardy Ferentschik <hardy(a)hibernate.org&gt; >> >> >> 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(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 > > _______________________________________________ hibernate-dev mailing list hibernate-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev

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(a)gmail.com&gt; > To: "Sanne Grinovero" <sanne(a)hibernate.org&gt; > Cc: "Hibernate Dev" <hibernate-dev(a)lists.jboss.org&gt; > 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(a)hibernate.org&gt; 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(a)hibernate.org&gt; 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(a)hibernate.org&gt; > > > 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(a)hibernate.org&gt; 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(a)hibernate.org > > > > > >> > wrote: > > >> >> > > >> >> On 29 May 2015 at 08:15, Emmanuel Bernard < emmanuel(a)hibernate.org&gt; > > >> >> wrote: > > >> >> > > > >> >> >> On 28 May 2015, at 10:42, Hardy Ferentschik < hardy(a)hibernate.org&gt; > > >> >> >> 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(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 > > > > > > > > _______________________________________________ > > 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 > _______________________________________________ hibernate-dev mailing list hibernate-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev