[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [riena-dev] Riena provisional APIs
|
hi scott
if you read closely you see that I did not compare Riena and ECF. What
I said was that if even a project like ECF has to break its APi at one
stage it is very likely that this will also happen to Riena. I dont
see that as a indication that we should keep all our APIs provisional.
When we released 1.0.0 we consulted with PMC and EMO and my impression
from the email conversation there was that it should be the rule that
every Eclipse project that is no longer in incubation should in
general follow the API guidelines from Eclipse. And that is all I was
saying.
christian
Am 06.04.2009 um 16:34 schrieb Scott Lewis:
Hi Christian,
Christian Campo wrote:
Hi Scott,
too me the difference between provisional API and non-provisional API
are just the rules that you need to follow when making breaking
changes.
This is one aspect, but I don't think your interpretation is shared by
all. I think you should consult the runtime PMC about this.
I agree that changes will happen only that I intend to supply a more
stable foundation so that people building apps on top of Riena can be
sure that it will
continue to run in the future unless they are explicitly notified
i.e.
through deprecation and through a new major version number.
Even ECF 3.0 now has breaking changes. So that tells me that if I
would wait until no API break can happen in Riena, my APIs will stay
provisional forever.
That's clearly not the intent (to stay provisional forever). And WRT
ECF...ECF is at version 3, not version 1...after 4+ years as an
Eclipse
Foundation project and 2+ years incubation period...so this is not
exactly comparable.
Again, I suggest you consult the RT PMC about this before making a
final
decision.
Scott
_______________________________________________
riena-dev mailing list
riena-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/riena-dev
