Hi, Greg Hogan <c...@greghogan.com> writes:
[...] >> The question isn’t (not at all!) *if* we should remove, yes we must >> remove old and/or broken packages. The question is *how*, i.e., we need >> to have a common understanding, both end: What does it mean include a >> new package? What does it mean “it’s safe to remove”? >> >> I think a GCD is the way to go but these days I’ve enough on my plate so >> I cannot commit to draft something before the next months. If someone >> wants to start, I’ll join with the pleasure! :-) > > +1 to a GCD. Ideally the surprises could be automated away. Don't we already have a deprecation policy? What's missing from it? I don't think a GCD is needed to adjust our policy, if needed, especially if it's to relax it. -- Thanks, Maxim
