Re: [eclipse.org-planning-council] Simultaneous ReleaseBrainstorming

[Nick Boldt <nboldt@xxxxxxxxxx>]

So... should we say it's OK to deprecate anything for any of the .0, .1, .2, or .3 releases, but you can only remove API once (or twice) a year? 

On Thu, Oct 5, 2017 at 11:25 AM, Mélanie Bats <melanie.bats@xxxxxxx> wrote:

Le 05/10/2017 à 17:24, Daniel Megert a écrit :

 > 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.

Deprecation is not bad just we should insure that we still have enough time before deletion to update depending projects.

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

*Obeo*
25 Boulevard Victor Hugo - Colomiers - France
http://www.obeo.fr
_______________________________________________
eclipse.org-planning-council mailing list
eclipse.org-planning-council@eclipse.org
https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council

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.

--

Nick Boldt

Senior Software Engineer, RHCSA

Productization Lead :: JBoss Tools & Dev Studio

IM: @nickboldt / @nboldt / http://nick.divbyzero.com

TRIED. TESTED. TRUSTED.

@ @redhatnews      Red Hat