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

["Daniel Megert" <daniel_megert@xxxxxxxxxx>]

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

Dani



From:      
 Mélanie Bats <melanie.bats@xxxxxxx>
To:      
 eclipse.org-planning-council@xxxxxxxxxxx
Date:      
 05.10.2017 17:18
Subject:    
   Re: [eclipse.org-planning-council]
Simultaneous ReleaseBrainstorming
Sent by:    
   eclipse.org-planning-council-bounces@xxxxxxxxxxx

---

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
CTO
+33 7 87 69 42 84
+33 5 34 57 16 29
@melaniebats

*Obeo*
25 Boulevard Victor Hugo - Colomiers - France
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.obeo.fr&d=DwIGaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=1UITCR5rxUZHSFczvfaNFK4ymEbEiccRX7VKchpqz0Y&m=YGb9TQm6jiT96ZRTr3Rg3Yaa6qlb1wHW244jAjaMC3Q&s=JUKNdtaKHVP0zBEgy2ufeNp-ifpX2fBMTB9YV2-CzRQ&e=
_______________________________________________
eclipse.org-planning-council mailing list
eclipse.org-planning-council@xxxxxxxxxxx
https://urldefense.proofpoint.com/v2/url?u=https-3A__dev.eclipse.org_mailman_listinfo_eclipse.org-2Dplanning-2Dcouncil&d=DwIGaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=1UITCR5rxUZHSFczvfaNFK4ymEbEiccRX7VKchpqz0Y&m=YGb9TQm6jiT96ZRTr3Rg3Yaa6qlb1wHW244jAjaMC3Q&s=eC6ODZRDGP5ZIeHOeSRdf1huAAv9FjWBYSumnuNYE5s&e=

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.