On Mon, September 25, 2006 11:07 pm, Matt Mullenweg wrote: > Robert Deaton wrote: >> I think its a good case for leaving it in 2.1 and indefinitely. Like I >> said before, even if we put a giant glaring message saying "We now >> recommend the use of the XML export." Or, although this would never >> happen, we could remove it from future versions and supply a seperate >> upgrade package which will always include the latest version of the >> plugin for just this purpose. > > For a major release we can note the change in the announcement post. > We've done in the past when removing plugins and it seems to have worked > well. I remember a huge ruckus when Markdown/Textile was removed. > > Hopefully by that point someone will have picked development back up on > the abandoned plugin or we can point to a feature-equivalent alternative > for creating SQL dumps. (Though I suppose if not, we can just point > people to phpMyAdmin.) >
I've contacted skippy and am willing to take over the onward development of the wp-db-backup plugin. I find it extremely usefull and would like to see it flourish as it provides a different kind of service to the XML import/export which is still very usefull. westi -- Peter Westwood <[EMAIL PROTECTED]> http://blog.ftwr.co.uk _______________________________________________ wp-testers mailing list [email protected] http://lists.automattic.com/mailman/listinfo/wp-testers
