On Wed, Jan 12, 2005 at 09:29:40AM +0100, Osamu Aoki wrote: > On Sat, Dec 18, 2004 at 05:32:48PM -0800, Steve Langasek wrote: > > On Sun, Dec 19, 2004 at 02:48:02AM +0200, Antti-Juhani Kaijanaho wrote: > > > Like with many other things in Debian, how you do it doesn't matter as > > > long as you don't break things. Things that should be considered > > > include: > > > > > - Use a -1 Debian revision number for the new upstream release. > > > > > - Preserve old changelog entries (sounds obvious, but there have been > > > incidents...) > > > > > - Add an entry "New upstream release" to the changelog.
> > ... and please note that "New upstream release" is not a change that closes > > bugs other than wishlist requests *for* the new upstream release; if there > > are changes *in* the new upstream release that fix reported bugs, please > > enumerate those changes before closing the bugs in the changelog. > Noted in CVS version of maint-guide. > # Describe concisely the changes in the new upstream release that fix > reported bugs and close those bugs in the changelog. > # Describe concisely the changes to the new upstream release by the > maintainer that fix reported bugs and close those bugs in the changelog. Sounds good to me, thanks. -- Steve Langasek postmodern programmer
signature.asc
Description: Digital signature
