Re: what needs to be policy?
Manoj Srivastava <srivasta@golden-gryphon.com> writes:
> You can innovate all you want -- as long as the old method in
> policy is supported (which you say you support). But you can't report
> bugs against packages for using the old method -- until you pass the
> new method (after it stabilizes) through policy.
>
> And that is a good thing.
>
> Now that I have taken care of the innovation objection, do you
> agree?
>
> Interfaces, after they stabilize, and if they are supposed to
> be mandatory, or affect a large number of packages, should still be
> made a standard, and modification of standards should not be under
> control of any one person.
I support this, it makes good sense to keep the policy method, for backward
compatibility, while innovating.
Martin.
Reply to: