Ariel Constenla-Haile wrote:
Hello Juergen,
On Thursday 14 May 2009, 10:34, Juergen Schmidt wrote:
i would like to suggest that we start new threads to discuss proposals
for API changes with a subject
API.CHANGE-<ver>: ....
e.g.
API.CHANGE-4.0: ....
is this <ver> the current version where the to-be-changed API appears, or
the version where it will be integreted? in the later case, quite
impossible to guess.
sorry for being unclear, it should be the version for which the change
is proposed. Well you are correct that it is not easy to say 100%. But i
think if somebody will change an API he/she has of course a specific
release in mind, probably the next possible major release.
is there already a general agreement about when API changes will be allowed?
only major (for example only OOo 4.0, OOo 5.0), or also minor (OOo 3.3, OOo
3.4), or even micro (OOo 3.2.1)?
mmh, i think yes, we should take it serious and should allow this
changes not frequently and only for major changes. We still have the
published keyword that allows us to improve new APIs over minor releases
as well.
By all the inconvenience with stable and compatible APIs they have of
course many advantages as well. We shouldn't forget this.
Juergen
It should be
just for the discussion. A complete list with all changes for a major
release is necessary anyway and will be available in the wiki.
may be http://development.openoffice.org/releases/3.1_sdk.html can also be moved
to the wiki, so that one can keep track of them, something like
http://wiki.services.openoffice.org/wiki/API/SDK/Features/3.1
Interpret it more as PROPOSED.API.CHANGE-4.0 but i wanted keep it
shorter. Maybe you have a better idea?
mmm... no, sorry for the lack of imagination.
Regards
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
