Comment 13 for bug 275375

I just started testing 1.0.7, and I've already discovered some bugs. (One in the packaging, and one in the program).

I think maybe we need to change how we think of this program. Instead of thinking of it as an upgrade, just think of it as a new program, which is what it is. At a minimum, you could leave the old deluge packages in jaunty, with the deluge name, and add the new deluge as deluge1. This is done with things like grub and java, so I think it would make sense.

Thus, you can incorporate deluge1 now, leave deluge0 for those who don't want to upgrade without an upgrade path, and then merge later on. (though, personally, I don't care about the loss of settings. It keeps the torrents, which is good enough for me.)

Question: since deluge0 is essentially an abandoned project, does it make sense to invalidate all the outstanding bugs in launchpad?

Lastly, the last caveat is a feature, not a drawback. You can still run the daemon all you want, but the default setting for the GUI is to attach itself to the local daemon, and close it when you close the GUI. This is what a single user expects. But, if you want to run the daemon on an ongoing basis, you either have to disable "classic mode" for the gui, or use the web and cli UIs. Anyway, its not that important. Normal users won't notice, and the help docs seemed clear enough for the power users IMHO.