On 02/17/2015 11:48 AM, Matthew Toseland wrote: > On 17/02/15 14:36, Florent Daigniere wrote: ... >> 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. > Generally fair, but just to be clear: When API changes are a necessary > part of a paid developer's work, they should not generally be expected > to fix unofficial plugins. Obviously if an official plugin is broken by > core fred changes, the dev should fix that. > > Reasonable?
It seems reasonable to me, and reiterates why breaking API is painful and not at all to be done lightly or quietly: it breaks more code than one can be expected to fix or even know about. Freenet is less useful as a platform the more it's a moving target for for application developers. I hope that saces' and nextgens' movement toward OGSi and explicit API versioning will allow a stable API to be clearly defined and maintained.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Devl mailing list Devl@freenetproject.org https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
