-----BEGIN PGP SIGNED MESSAGE----- Ok, second proposal:
The "distributed", non i386-centric one: The debian-devel-changes is renamed to debian-devel-changes-i386, and an announcement is sent explaining the goal of the new list. There would be the following lists: a) debian-devel-changes-<arch> for every <arch>. b) debian-devel-changes-source. And the announcement policy would be: * Every time an upload includes any package which may be used by <arch>, it should be announced in debian-devel-changes-<arch>. This includes arch-independent uploads, i.e. every time the dinstall program installs a file *or a symlink* in the binary-<arch> directory, there is an announcement for it. * Every time an upload contains source of any kind, it should be announced in debian-devel-changes-source also, i.e. every time the dinstall program installs a new file in any of the "source" directories, there is an announcement for it. Benefits: * Users of the <arch> architecture would have to subscribe *only* to the debian-devel-changes-<arch> list (convenience for the users as a primary goal). * Although a binary-all upload would be announced in seven lists, this is not a waste of bandwidth, because subscribers of the different debian-devel-changes-<arch> lists would normally not overlap. * Developers looking for new source packages would have to be subscribed to just one list also, debian-devel-changes-source. * Most "source i386" uploads would go both to the debian-devel-changes-i386 list and to the debian-devel-changes-source list. This, again, is not such a waste of bandwidth, considering that the number of subscribers of debian-devel-changes-source would be really low. Please, accompany your objections with a more better proposal :-) -----BEGIN PGP SIGNATURE----- Version: 2.6.3ia Charset: latin1 iQCVAgUBNc7VeiqK7IlOjMLFAQFnQwP/fmjK6L1PutXOv70EG5+y5tsAP4k/W8Ee bFJIgL+M1ZTr7anOA6KB2VqJO7xTAfxMCwuK45Id+C7vrZEUX8606yU39nfcYMgZ ujTsbFDJp4N3Caf/QESFPcS3UFFHLLd7yuuU4cKP+kUMY4iDZjMQoVHaan8Kr3iW mldb0+cPr5w= =8WPG -----END PGP SIGNATURE-----
