Scott, On Fri, Apr 12, 2013 at 11:31:09PM -0600, Scott Long wrote: S> One thing that FreeBSD is bad about (and this really applies to many open source projects) when deprecating something is that the developer and release engineering groups rarely provide adequate, if any, tools to help users transition and cope with the deprecation. The fear of deprecation can be largely overcome by giving these users a clear and comprehensive path forward. Just announcing "ipfilter is going away. EOM" is inadequate and leads to completely justified complaints from users. S> S> So with that said, would it be possible to write some tutorials on how to migrate an ipfilter installation to pf? Maybe some mechanical syntax docs accompanied by a few case studies? Is it possible for a script to automate some of the common mechanical changes? Also essential is a clear document on what goes away with ipfilter and what is gained with pf. Once those tools are written, I suggest announcing that ipfilter is available but deprecated/unsupported in FreeBSD 10, and will be removed from FreeBSD 11. Certain people will still pitch a fit about it departing, but if the tools are there to help the common users, you'll be successful in winning mindshare and general support. The task to write a migration guide is already a task for maintainer, and the thread is to search one. If lack of migration guide doesn't allow us to remove in 10.x cycle, I doubt the guide will appear in 11.x cycle, 12.x, etc. So we will live with ipfilter forever. What I can do, is to resend email to the stable_at_ list. Also, I can add the deprecation WARNING to stable/9 unless we find maintainer prior to 9.2 branching. -- Totus tuus, Glebius.Received on Sat Apr 13 2013 - 15:34:17 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:36 UTC