-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160
> what to do about having something around that you can refer people who > want to run 4.x (???!!!). Is a simple information tidbit "if you > want to use xxx, you use version x.y.z version of DBD::mysql" ? > What have others done about this issue? Yes, it is basically as simple as that. Some thoughts: * Make your abandonment of old versions in large chunks, don't simply phase out older versions over time. In other words, consolidate the pain into as few releases as possible. Ideally, one every 10 years. :) * Have a version or two with lots of warnings in the docs before making the change. * Make the change at a major version bump. Then you can tell people they need version x, rather than x.y.z * This is also a good time to break other things - such as requiring a newer version of DBI. Consolidate that pain! * Provide instructions in the docs about how to reach the old versions. Have the frozen version available somewhere other than CPAN too. * Expect people who have been living off of those #ifdefs for years to suddenly crawl out of the woodwork after you flip the switch and complain. Anticipate their complaints in your docs so you can simply point them there. (MySQL 4.x? I know places still running 3.x!) - -- Greg Sabino Mullane g...@turnstep.com End Point Corporation http://www.endpoint.com/ PGP Key: 0x14964AC8 201309262247 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iEYEAREDAAYFAlJE8t0ACgkQvJuQZxSWSsgCxACgxPsWn+WT1LvbtCFIBzdeKUnk QS8AoJjZIYPUPJHBi71ynghGWN+4qRRx =88jH -----END PGP SIGNATURE-----
