[beta-3.0] TODO list (draft proposal)
Hi all,
this weekend I sat down and wrote a list of what I think should be done
with the beta packages of 3.0. By the way, I have both of them (*base
and *bin) in a state that patches are applied cleanly and
dpkg-buildpackage runs fine for a source and binary upload. I'm
currently putting them on http://people.debian.org/~frank/, but that
takes quite some time (the ssh encryption seems to create considerable
overhead).
So here's the TODO list I propose, comments, additions or deletions
wellcome:
1. Check whether the symlinks that we create are still working (and fix
if necessary)
2. Check whether update-* utilities still work (and fix)
3. Check for newly included or missing programs in tetex-bin (and write
manpages, etc.)
4. Preliminary tests of the main programs (should be no problem)
5. Upload to experimental, announce on devel and personally to
maintainers of packages that depend on our packages. Also upload
libkpathsea3.
6. Bug cleanup.
6.1 First, I would suggest to categorize the bugs, along the
line:
- yet tagged with "fixed-upstream"
- reproducible, example file exists
- irreproducible/moreinfo
- obviously packaging related
- other
6.2 Check the packaging related bugs. And fix them, yes.
6.3 Try to get information on the irreproducible/moreinfo bugs, or
close them
6.4 As soon as 3.0 is released, check all the bugs with example
file.
While we're doing 6., there's a couple of decisions to be made:
a) Do we want more splitting (besides the xfonts stuff)?
b) Do we want to switch to ucf (I'm voting yes)
c) Do we want to write a policy (see separate mail)?
cc) Do we want to establish a dpkg mechanism so that add-on packages
don't need to run update-* in their maintainer scripts, but it's
done once after all packages are installed?
Regards, Frank
--
Frank Küster, Biozentrum der Univ. Basel
Abt. Biophysikalische Chemie
Reply to: