Plugin auto-update is implemented and apparently working. More could be done to 
improve it, of course, but it looks like it should be sufficient for plugin 
updates to be released and deployed without having to deploy a new fred build 
to force them. New builds are distributed through USKs, just as with fred 
builds, and when they are downloaded, fred asks the user whether they want to 
update the plugin. If they say yes, we do a final check of the revocation key 
and then deploy the new version of the plugin.

This should be enough for us to deploy WoT, Freetalk, and FlogHelper (and maybe 
more things e.g. digger3's IRC work?) as semi-official plugins, not bundled, 
marked as beta, but downloadable through the plugins page. Is it? (When) should 
I deploy these plugins?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 835 bytes
Desc: This is a digitally signed message part.
URL: 
<https://emu.freenetproject.org/pipermail/devl/attachments/20091120/d4a73b09/attachment.pgp>

Reply via email to