[prev in list] [next in list] [prev in thread] [next in thread] 

List:       vcs-pkg
Subject:    Separate branch for experimental)
From:       liw () iki ! fi (Lars Wirzenius)
Date:       2007-10-31 22:22:45
Message-ID: 1193865741.5718.2.camel () dorfl ! globalsuite ! net
[Download RAW message or body]


On ke, 2007-10-31 at 21:55 +0100, martin f krafft wrote:
> also sprach Kumar Appaiah <akumar@ee.iitm.ac.in> [2007.10.31.0219 +0100]:
> > All this is just perfect. I still have just one issue. Can I share the
> > changelog across branches? I mean, can I separate the changelog alone
> > into a separate branch, and merge it into master and experimental (a
> > new branch) before the build?
> 
> We need to get rid of the changelog-as-a-file concept and build the
> changelog from commit log entries in the build branch. git-dch (part
> of git-buildpackage), which I have not yet tried, might be a step in
> the right direction. See Sam's response.

Soon after I switched from CVS to Bazaar (bzr), I stopped using
changelog files. Instead, before I make a release, I update a NEWS file
which summarizes the changes since the previous release, and also add a
dump of the commit messages (bzr log --long --verbose, more or less) to
sit next the tarball, but that is not included in the package itself.

So far I'm happy with this solution.


[prev in list] [next in list] [prev in thread] [next in thread]