On Wed, Oct 07 2009, Raphael Hertzog wrote:
> On Tue, 06 Oct 2009, Manoj Srivastava wrote:
>> Do we really need to have policy to tell people not to create buggy
>> packages?
>
> Well, there are people out there that don't know that doing such things
> are bugs. I would like to be able to ede them pointing to our policy,
> explaining that it's what makes of us a quality distribution.
This by itself does not meet the criteria for inclusion in
policy. There are all kinds of things that are bugs, and are not
mentioned in policy; and adding them to policy is needless bloat. If
you wish, a new document can be started somewhere, about common
mistakes, and this can fit well in there.
>> Policy is not, after all, a club to beat people on the head
>> with.
>
> It is however a required reading for any new maintainer.
Again, that is a reason to keep the policy document from bring
bloated, and prevent mission creep.
>> The size and density of the policy manuals are always an issue,
>> and it seems to me that these are obvious bugs that are already covered
>> by release manager requirements and bug reporting guidelines; adding
>
> Where ?
Well, for the latter:
http://www.debian.org/Bugs/Developer
Since changes in interfaces will make unrelated software break,
For the former, I think it would be a decent addition to a
document like
a) http://release.debian.org/lenny/rc_policy.txt
or, failing that, the developers reference as a "Good Practice".
I just don't see this as a policy matter.
manoj
--
Some people only open up to tell you that they're closed.
Manoj Srivastava <sriva...@debian.org> <http://www.debian.org/~srivasta/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
--
To UNSUBSCRIBE, email to debian-policy-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
