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

["Daniel Megert" <daniel_megert@xxxxxxxxxx>]

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

How much breakage we want to allow is
part of the ongoing discussion. I'd vote for once per year. I don't think
allowing API breakage is really the important part. We want to bring features
more frequent to our clients and breaking clients is mostly not required
to achieve this. As for the difference, it is much simpler for developers
since they only have to deal with one stream.

Dani



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

---

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

Le 5 oct. 2017 à 17:09, Daniel Megert <daniel_megert@xxxxxxxxxx>
a écrit :

> 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@xxxxxxxxxxxto request removal.


_______________________________________________
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@xxxxxxxxxxx
https://urldefense.proofpoint.com/v2/url?u=https-3A__dev.eclipse.org_mailman_listinfo_eclipse.org-2Dplanning-2Dcouncil&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=1UITCR5rxUZHSFczvfaNFK4ymEbEiccRX7VKchpqz0Y&m=ugtbNsgzr9jIYJNg13EIJ0h-REhEe-ezYKIgwUh2Zb8&s=BtzOw_UMGbNRz6d2yTXFhIpaZKLZaq-MW7VS91CoQfk&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.