Re: HAMM FREEZE IS ONE WEEK AWAY
On Sat, 7 Mar 1998, Brian White wrote:
> Just a reminder to everyone that, barring exceptional circumstances, Hamm
> will be frozen on March 16th. I will be restricting uploads at that point
> to bug-fixes only. I'll also be removing all non-essential packages that
> still have critical, grave, or important bugs open.
>
> Please try to clean up any outstanding bugs so we can have a reasonably
> clean system for the testing group to work on.
Two notes to the code-freeze:
1. It's important that we get all orphaned packages out of the archive
when doing the freeze since a release should not contain orphaned
packages. I was planning to set up the Developer DB to simplify this
process, but I guess we won't get it up and running and filled with data
so we could use this within one week.
Does someone have any other ideas to detect orphaned packages? (Perhaps
something like a maintainer ping. Richard mentioned that he has some nice
ideas...)
Note, that a few people wanted get all packages approved by their
maintainers. The idea was, to not include all packages in stable
`automatically,' but only if the maintainer explicitely says so. Is there
a way we could accomplish this without big troubles?? (Having to approve
1800 packages is some work... :)
2. Currently, the results from the Lintian checks have not been reported
to the bug tracking system yet. Though, I don't think that reporting all
errors as bugs makes sense, we definitely should report the more
`important' errors as bugs to get the corresponding packages fixed before
the release.
Here is a list of tags which I would consider as `important', thus
`release-critical.' (The numbers indicate how many packages currently are
affected.)
N: bad-link-to-undocumented-manpage(7)
N: control-file-has-bad-owner(12)
N: debmake-templates-in-copyright(7)
N: file-in-usr-local(1)
N: ldconfig-symlink-missing-for-shlib(8)
N: libc5-binary(66)
N: md5sum-mismatch(4)
N: md5sums-lists-nonexisting-file(63)
N: no-copyright-file(178)
N: special-file(1)
The `libc5-binary' tag is on this list because it was the major release
goal of "hamm" to get everything ported to libc6. However, porting some of
the programs might be a lot of work so we might not consider these as
`Important' bugs. Comments?
All the other tags are very easy to fix. Of course, one could argue that
some of these errors are not `release-critical'. But the maintainers have
enough time to fix their packages. If someone doesn't have time to fix
these simple bugs within, say 4 weeks, I'd consider the package as
`orphaned'. (After all, NMUs are still possible.)
Please give me comments on the list above. If I don't hear any comments
until tomorrow morning, I'll start sending 313 `important' bug reports...
Thanks,
Chris
-- Christian Schwarz
schwarz@monet.m.isar.de, schwarz@schwarz-online.com,
Don't know Perl? schwarz@debian.org, schwarz@mathematik.tu-muenchen.de
Visit PGP-fp: 8F 61 EB 6D CF 23 CA D7 34 05 14 5C C8 DC 22 BA
http://www.perl.com http://fatman.mathematik.tu-muenchen.de/~schwarz/
--
E-mail the word "unsubscribe" to debian-devel-request@lists.debian.org
TO UNSUBSCRIBE FROM THIS MAILING LIST. Trouble? E-mail to listmaster@debian.org .
Reply to: