Earlier, I wrote: >> (6) Get his new key signed by a couple of people, upload it to the >> keyservers as usual, and start using it.
On 12/11/2011 06:25 AM, bdfhjk wrote: > OK, but what with image license? We should wait until he make new > key and then ask about signing their statement? Yes. By definition, he can't sign it with his old lost one :) There might be a way for him to embed a copyright string and licence notice inside the original SVG file, and for those to be retained when it is converted in the build process to PNG or whatever other binary formats we need. That approach might be worth a look, if the GPG key problem is going to take a while to sort out. OVERALL STATUS: Can you post a summary of what you think the current status of clicompanion 1.1 is, first in terms of the application itself, and second its packaging? Is the application itself 100% ready for declaring to be clicompanion 1.1 and being released as a source tarball? If not, what else needs to be done with it to reach that point? According to https://blueprints.launchpad.net/clicompanion/+spec/release-plan-1.1 we have had some testing "IN PROGRESS" for the last couple of weeks... are there any status updates on how that is going? Are there any release critical bugs remaining that we know of? Thanks, Jonathan -- Mailing list: https://launchpad.net/~clicompanion-devs Post to : [email protected] Unsubscribe : https://launchpad.net/~clicompanion-devs More help : https://help.launchpad.net/ListHelp
