Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [] Simultaneous ReleaseBrainstorming

> we should forbid deprecation on each version,

What is bad with deprecating an API? It does not cause any harm except for additional warnings in the code.


From:        Mélanie Bats <melanie.bats@xxxxxxx>
Date:        05.10.2017 17:18
Subject:        Re: [] Simultaneous ReleaseBrainstorming
Sent by:

Le 05/10/2017 à 17:14, Mikaël Barbero a écrit :
> No worries, it was way too abstruse.
> You said that we could convert update releases to normal releases, but
> we should probably allow breakage in only one or two. Then, what is the
> difference between an update release and a normal release where breakage
> is not allowed?

My feeling is that that we sould allow breakage on each new version but
we should forbid deprecation on each version, I mean we could introduce
API breakage wherever we want but we should keep the old APIS long
enough that each depending projects get time to update.

Mélanie Bats
+33 7 87 69 42 84
+33 5 34 57 16 29

25 Boulevard Victor Hugo - Colomiers - France
_______________________________________________ mailing list

IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation.  To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.

Back to the top