[Debtags-devel] Re: Proposal: Bringing volatile in shape for sarge

[Thaddeus H. Black]

--Dxnq1zWXvFF0Q93v
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

When you were first proposing volatile last year, I
asked if you would allow final debram-data in
volatile.  If you can remember, this is a very unusual
special case, because debram-data is not volatile in
the same way clamav is.  The matter with debram-data
is that

  1. final debram-data inherently depends on sarge's
  final package list, but

  2. sarge's final package list is not available until
  sarge's release, so

  3. it is fundamentally impossible to ship final
  debram-data with sarge.

With Steve Langasek's advice, we do have an adequate
almost-final debram-data now in sarge.  The almost-final
debram-data covers almost all of sarge, so it is pretty
good.  Still, I would like to ask your permission, in
principle, to distribute the final debram-data via
volatile after the release.

If so, very good.  If not, then we would distribute the
final debram-data on Sourceforge and/or the Debtags
Alioth website, as originally planned.  Volatile would
seem more natural, however.  Permission, please?

If language to amend volatile's "acceptance rules" is
helpful, here is one possibility:

   * volatile is not "just another place" for
     backports, but should only contain changes to
     stable programs that are necessary to keep them
     functional;

+  * as a special exception, data packages which
+    fundamentally cannot be finalized in time for
+    the release, because their data depend on the
+    very contents of the release, may be
+    distributed in volatile (note that this does
+    not include late packages which merely miss the
+    freeze deadline);
+

--=20
Thaddeus H. Black
508 Nellie's Cave Road
Blacksburg, Virginia 24060, USA
+1 540 961 0920, t@b-tk.org

--Dxnq1zWXvFF0Q93v
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iEYEARECAAYFAkKTloUACgkQh3E0gzgBXn5V2gCfR37hLn+P7puxFTRWB5TNFlMX
M1oAn1oTjzARksmGZ1bZkAYC5U9wgzfc
=pTcU
-----END PGP SIGNATURE-----

--Dxnq1zWXvFF0Q93v--