[Pkg-shadow-commits] r427 - branches/experimental

[Nicolas FRANCOIS]

Author: nekral-guest
Date: 2005-08-01 20:07:01 +0000 (Mon, 01 Aug 2005)
New Revision: 427

Added:
   branches/experimental/TODO
Log:
Here are some points I would like to see resolved before the experimental
package enters unstable.


Added: branches/experimental/TODO
===================================================================
--- branches/experimental/TODO	2005-07-29 17:21:47 UTC (rev 426)
+++ branches/experimental/TODO	2005-08-01 20:07:01 UTC (rev 427)
@@ -0,0 +1,46 @@
+
+Things that should be done before the upload to unstable
+ * Verify the patch between Debian 4.0.3 and 4.0.11.1 (It should be
+   sufficient, even if 4.0.12 is eventually uploaded)
+ * clean up debian/rules (and other packaging files)
+ * read the changelog/NEWS files
+ * the experimental branch is stabilizing, the patches directory can be cleaned
+   + series is full of commented patches
+   + the patches directory is full of not needed patches
+   + the patches may be in the wrong section (3xx/4xx), becausethe patch
+     was applied upstream, but there is still some small issues.
+   + the headers of the patches may be outdated
+   + It would be nice to have the program and man page correction in the
+     same patch
+ * other queries on debian-devel:
+   + with or without SELINUX
+     How to test if this work with a SELINUX enabled Debian?
+   + is the dialup functionality used?
+   + mkpasswd?
+   + should PAM session be closed as root?
+ * push all our l10n patches upstream (program PO should already be pushed
+   upstream, man pages probably not). Maybe we should wait the new man page
+   translation process.
+ * There are probably some points to add in NEWS
+ * Coordinate a release with Marc Haber (adduser)
+
+Other points (not related to the release of a syncronized shadow):
+ * su concatenation of arguments anouncement on debian-devel
+ * compare the source with the usages and man pages
+ * do something (a tool) for the variables in login.defs
+   In Debian, some tools are not compiled with the PAM support, so upstream
+   getdef.c won't be OK.
+   It should be nice to see in each man page the set of variables used.
+   The Debian package can now compile (export DEB_BUILD_OPTIONS='nostrip debug')
+   with the debugging informations. This may be used to extract the set of
+   variables used in Debian/for each tools.
+ * verify all the patches around (I've found patches for at least RedHat,
+   OWL, LFS, Mandriva, Gentoo; are they already applied?)
+ * make a testsuite
+   + all options could be tested
+   + by reading the man page and writing some small tests for each
+     functionnality (and testing the limit cases, we can probably find
+     a lot of small/documentation bugs)
+     e.g. test chage with some fields set to 0
+          test chage with a date argument instead of a number of days
+