Re: About the Hamm Freeze
> >Because of this, there was a small window where uploads were made expecting
> >to make it into Hamm before the freeze. If your package did not make it,
> >then the easiest thing to do is to reupload it to Incoming with a distributi
> >on
> >of "frozen unstable" on the first line of the "changelog" file. Also be
> >sure the changelog states very clearly what has changed. I'll be trying
> >to limit changes in Hamm to bug-fixes only. All critical, grave, and
> >important bugs _must_ be marked as done before a packages will be allowed
> >into Hamm.
>
> I thought the bug-closing policy was that I shouldn't close bugs until I
> got notification that the package had been installed into the distribution.
> Is this policy suspended in respect of frozen? or do I have to upload to
> somewhere else first?
As long as the changelog states which bugs this version fixes, I'll
still know which bugs are done. It isn't necessary to close them
before installation. The package just has to fix the bugs.
Brian
( bcwhite@verisim.com )
-------------------------------------------------------------------------------
Friends are relatives that you make for yourself.
--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: