kde release changelog idea

Waldo Bastian bastian at kde.org
Thu Oct 14 11:02:10 BST 2004

On Thursday 14 October 2004 03:33, Michael Pyne wrote:
> On Wednesday 13 October 2004 07:53 pm, Benjamin Meyer wrote:
> > Rather than have maintainers update changelogs, wouldn't it be possible
> > to have a bugzilla report that showed bugs closed during that minor
> > release time?
> I like that idea, but I know that I've fixed a few bugs in JuK for
> 3_3_BRANCH that didn't have bug reports.  We would need some way to
> manually add bugs that we've fixed, unless we want to open a bug report and
> immediately close it or something. :-/

In one of my previous jobs you couldn't check in any changes if you didn't 
have a work/bug report number to go with it. When a new release was made you 
could ask the source repository a list of all bugs that were fixed in the 
period since the previous release.

But even if you don't have bugnumbers for every fix, it would still make it 
easier to keep track of those changes that DO relate to an existing 

> Also, just because a bug is closed doesn't mean it was fixed in BRANCH, we
> would need some way of determining that a bug has been closed in BRANCH.

I wonder how hard it is to extend bugzilla to register for bugs in which 
branch(es) they have been fixed. The other approach is to extract the 
bugnumbers from the CVS commit messages. In that case you must make sure to 
always mention the bug when commiting, e.g. as part of CCMAIL

Maybe we can add a "DONE: <bugnr>" header to close bugreports from the CVS 
commit message (alias for CCMAIL: <bugnr>-done at bugs.kde.org) and "BUG: 
<bugnr>" (alias for CCMAIL: <bugnr>@bugs.kde.org) to promote that practice.

bastian at kde.org   |   SUSE LINUX 9.2: Order now!   |   bastian at suse.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20041014/eac995a1/attachment.sig>

More information about the kde-core-devel mailing list