On 17/02/15 14:36, Florent Daigniere wrote: > We've just had a long chat with operhiem1 on IRC about release > management: > > The outcome is that 1468 will ship soon but not with the fcp/event-based > changes (5kloc of code, hundreds of commits). The release has been > stalled for too long, for no valid reason. The main argument is: > > 13:55 <@operhiem1> Event-based is better in the long run but no one has > use for it right now, so it's not release-blocking. > > 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. > > 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?
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Devl mailing list Devl@freenetproject.org https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
