[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Conflicts between developers and policy


	This, I like.
   Policy should be followed, except where a discussion about the clause in
   question is still ongoing, in which case the maintainer may indulge in a
   policy violation if they feel it is a technically superior

   When policy is being violated in this manner, this fact should/must
   be documented in the bug tracking system, on the appropriate Debian
   mailing lists, and in the changelog of the package violating
   policy, including information on what policy is being violated, and
   why.  Any permanantly accepted policy violations (such as the
   dynamic library managing programs being shipped statically linked)
   should/must be documented in the policy manual, including an
   explanation of why the policy exception was granted.

 Perfection is achieved only on the point of collapse. Parkinson
Manoj Srivastava  <srivasta@acm.org> <http://www.datasync.com/%7Esrivasta/>
Key C7261095 fingerprint = CB D9 F4 12 68 07 E4 05  CC 2D 27 12 1D F5 E8 6E

To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Reply to: