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?
Mikael
> 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.DaniFrom:
Mikaël Barbero <mikael.barbero@xxxxxxxxxxxxxxxxxxxxxx>To:
Eclipse Planning Council
private list <eclipse.org-planning-council@xxxxxxxxxxx>Date:
05.10.2017 17:03Subject:
Re: [eclipse.org-planning-council]
Simultaneous ReleaseBrainstormingSent 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._______________________________________________ eclipse.org-planning-council mailing list eclipse.org-planning-council@xxxxxxxxxxxhttps://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.
|