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

Re: Must and should again

>>"Julian" == Julian Gilbey <J.D.Gilbey@qmw.ac.uk> writes:

 Julian> (2) Developers' desires to know what "must" be done in all cases and
 Julian>     what "ought" to be done (but there may be exceptions), and what is
 Julian>     currently a "desirable thing" but is likely to one day become an
 Julian>     RC requirement.

 	This is what informative footnotes are for. They do not carry
 the weight of policy, but can onfrm people that this should
 directive shall, in the near future, become a must diurective,
 and they should plan accordingly. 
	Simple. Effective. And does not requirre wanking with the
 meaning of must, as defined by policy.

	We always had the solution -- there is not need to go back to
 the drawing board. 

 In the topsy-turvy world of heavy rock, it's often useful to have a
 nice, solid piece of wood in your hands. Ian Faith, manager of Spinal
Manoj Srivastava   <srivasta@debian.org>  <http://www.debian.org/%7Esrivasta/>
1024R/C7261095 print CB D9 F4 12 68 07 E4 05  CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C

Reply to: