You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@bookkeeper.apache.org by Flavio Junqueira <fp...@yahoo-inc.com> on 2011/05/19 10:35:50 UTC

CHANGES.txt

Hi, One quick question: should we have a CHANGES.txt file containing  
committed jiras as we have for zookeeper? If so, should it be per  
component or global?

My preference is to have this file updated upon every commit and have  
it on the project root, covering all components. This way will be  
easier when producing new releases.

-Flavio

Re: CHANGES.txt

Posted by Dhruba Borthakur <dh...@gmail.com>.

The CHNAGES.txt file has served us well in the hadoop land as well.

+1.

dhruba


On Thu, May 19, 2011 at 7:59 AM, Benjamin Reed <br...@apache.org> wrote:

> i agree. we need to add a CHANGES.txt.
>
> ben
>
> On Thu, May 19, 2011 at 1:35 AM, Flavio Junqueira <fp...@yahoo-inc.com>
> wrote:
> > Hi, One quick question: should we have a CHANGES.txt file containing
> > committed jiras as we have for zookeeper? If so, should it be per
> component
> > or global?
> >
> > My preference is to have this file updated upon every commit and have it
> on
> > the project root, covering all components. This way will be easier when
> > producing new releases.
> >
> > -Flavio
> >
> >
>



-- 
Connect to me at http://www.facebook.com/dhruba

Re: CHANGES.txt

Posted by Benjamin Reed <br...@apache.org>.

i agree. we need to add a CHANGES.txt.

ben

On Thu, May 19, 2011 at 1:35 AM, Flavio Junqueira <fp...@yahoo-inc.com> wrote:
> Hi, One quick question: should we have a CHANGES.txt file containing
> committed jiras as we have for zookeeper? If so, should it be per component
> or global?
>
> My preference is to have this file updated upon every commit and have it on
> the project root, covering all components. This way will be easier when
> producing new releases.
>
> -Flavio
>
>