ubuntu-accomplishments-contributors team mailing list archive

[Jono Bacon <jono@xxxxxxxxxx>]

On Mon, Jul 30, 2012 at 6:57 AM, Matt Fischer
<matthew.fischer@xxxxxxxxxxxxx> wrote:
> The problem with updating the changelog on each merge is that you have to
> roll the version.  For example, right now we're using 0.2. You'd either have
> to start updating the 0.2 changelog entry with new info or make a new 0.3
> entry.  Since 0.2 has shipped, you'd want to make a new entry, effectively
> changing the version.  What about just keeping a pseudo-changelog in tree or
> somewhere else on your system that becomes the real changelog during a
> release?

Agreed. I think if we have a file that we enter changes into and then
we cut and paste this into the Debian changelog, this will make most
sense.

    Jono

-- 
Jono Bacon
Ubuntu Community Manager
www.ubuntu.com / www.jonobacon.org
www.identi.ca/jonobacon www.twitter.com/jonobacon