How to handle newly added debian/changelog entries [was: Re: Bug#356573: [boson] I might as well do something good]

[Eddy Petrişor]

Hello all,

Just a suggestion for handling the debian/changelog file. (I have seen
this being done in other teams, too)

On 3/13/06, Gonéri Le Bouder <goneri at rulezlan.org> wrote:
> Le Dimanche 12 Mars 2006 23:59, Eddy Petrişor a écrit:
> > Hi,
> >
> > After my mistake, please add someting along th elines of:
> >
> > Index: debian/changelog
> > ===================================================================
> > --- debian/changelog    (revision 249)
> > +++ debian/changelog    (working copy)
> > @@ -1,3 +1,9 @@
> > +boson-base (0.11-4) UNRELEASED; urgency=low

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
I feel that the correct way to handle new versions is to place
"UNRELEASED" in the suite field instead of "unstable". This way it
will be known where one should add modifications and their logs in the
changelog.

I personaly was under the impression that 0.11-4 was already in Debian
unstable and somebody forgot to add a new changelog entry.

Also, please mark in the commit text (of svn) when the new entry in
the debian/changelog file was added, so is easier to track down.

Just before the preparation of the pakage the suite is changed, and
imediately after the build is done, a new changelog entry is added
(dch) and afterwards, manualy change the suite from unstable to
"UNRELEASED".


--
Regards,
EddyP
=============================================
"Imagination is more important than knowledge" A.Einstein