Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse.org-planning-council] Simultaneous ReleaseBrainstorming

> How an update release converted to a "normal" release without the permission to break API is different from an update release?

Sorry, I have troubles to parse this.

Dani



From:        Mikaël Barbero <mikael.barbero@xxxxxxxxxxxxxxxxxxxxxx>
To:        Eclipse Planning Council private list <eclipse.org-planning-council@xxxxxxxxxxx>
Date:        05.10.2017 17:03
Subject:        Re: [eclipse.org-planning-council] Simultaneous ReleaseBrainstorming
Sent by:        eclipse.org-planning-council-bounces@xxxxxxxxxxx




I see two main changes when converting the update releases to "normal" releases:
- It would probably allow (API) breakage like we allow with the yearly release. Not sure whether this is really something good for the community. We should identify just one, or maybe two, releases that allow breakage.


How an update release converted to a "normal" release without the permission to break API is different from an update release?

Mikael[attachment "signature.asc" deleted by Daniel Megert/Zurich/IBM] _______________________________________________
eclipse.org-planning-council mailing list
eclipse.org-planning-council@xxxxxxxxxxx
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.




Back to the top