"ext Ryan Abel" <[EMAIL PROTECTED]> writes: > Modest, in fact, seems to ENTIRELY substitute NB#'s for real > changelogs[2]. Quoting a recent Modest changelog: > >> modest (1.0-2008.26-1) hardy; urgency=low >> >> * Fixes: NB#83920, NB#86372, NB#86116, NB#84538, NB#84757, NB#85343 >> * Fixes: NB#85344, NB#85034, NB#83892, NB#84808, NB#84791, NB#82137 >> * Fixes: NB#83135, NB#85622, NB#86097, NB#86176, NB#85201, NB#84348 >> * Fixes: NB#81798, NB#85873, NB#85743, NB#84605, NB#81429 >> >> -- Dirk-Jan C. Binnema <[EMAIL PROTECTED]> Mon, 23 Jun 2008 11:01:57 +0300
I am guilty of this practice, too, (with the hildon-application-manager) but I think I have a semi-sane explanation: I use two files with change information: a GNU-style ChangeLog file in the top directory (or multiple of these in sub-directories), and Debian-style debian/changelog file. I use the GNU-style ChangeLog for detailed descriptions of changes to the source code (including bug numbers from both the internal and the maemo Bugzilla as background information), and I use debian/changelog for changes to the packaging bits in debian/. I also use debian/changelog for the magic "Fixes: NB#xxxxx." entries that are required by our development process to drive the internal Bugzilla. What I don't do, but should, is to maintain release notes in a GNU-style NEWS file. (I would not write individual release notes for the dozens of snapshots it takes until the OS is released, I would just write a single one describing the user visible changes since the last OS release.) _______________________________________________ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
