FYI, this plan might not be relevant anymore: I've fixed WOT to be backwards compatible to clients which use the old API. See [1]. Or in other words: This plan was a result of WOT not having been backards- compatible to existing plugins, which I did just fix.
> Going forward, release managers will frown upon any API breaking change > made. Especially if it's maid by paid developers, without much > consultation/interaction with the community and with the expectation > that volunteers will do the work to fix breakages the said API changes > will engender. This is not true. I have offered to deal with both official plugins and inofficial ones. But the compatibility fixes are not needed anymore anyway since I've just made WOT backwards compatible :) > We can't keep on delaying a release (it's been months already) featuring > important bug fixes on the basis that it breaks yet-to-be-released code > written by a paid developer. > > Florent Purge-db4o itself breaks all plugins, because toad has changed the fred callback interfaces. Did anyone sort out which ones have been fixed by volunteers yet? Because I likely should deal with the others. [1] https://github.com/freenet/plugin-WebOfTrust/commit/5f52b4a471fdff344e2ba49d21da08ab11ea95bc
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Devl mailing list Devl@freenetproject.org https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
