[hibernate-dev] Changelog file in Hibernate ORM

Steve Ebersole steve at hibernate.org
Mon Mar 4 11:40:59 EST 2013

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 at hibernate.org>
> To: "Sanne Grinovero" <sanne at hibernate.org>
> Cc: "Hibernate" <hibernate-dev at 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 at hibernate.org> wrote:
>>> On 2 Mar 2013, at 21:19, Sanne Grinovero <sanne at 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 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

More information about the hibernate-dev mailing list