On 03/08/2015 07:25 AM, Arne Babenhauserheide wrote:
> Am Sonntag, 8. März 2015, 10:20:17 schrieb xor:
>> I assume you made this suggestion of marking the new API unstable because:
>> 1) you then wouldn't have to wait for me to reply to your review results
>> 2) you didn't remember whether the review results contain any blocking 
>> issues 
>> when you talked with Arne.
> 
> I made this suggestion, because this is a new API and you cannot know
> how people will use it. Predominantly synchronous usage could change
> what people need to use the API efficiently.
...
> So please mark it as unstable (for a few releases), so people know
> that the API is open for change in case real life usage shows up a
> need for that.
> 
> In short: This has nothing to do with the quality of the code, but
> with community decision making processes

Well put - and agreed, this mirrors my reasoning. Tests using the API is
not sufficient to know how it will be useful to use it in client
applications.

I will merge this API as-is once it is marked as unstable. Maybe
something like

/*
 * This API is unstable. It will be improved in response to your
 * feedback.
 */

?

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Devl mailing list
Devl@freenetproject.org
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

Reply via email to