Re: [eclipse-pmc] Update Release Rules

["Daniel Megert" <daniel_megert@xxxxxxxxxx>]

As mentioned in our PMC call, I also like
that version!

Dani



From:      
 "Mike Wilson"
<Mike_Wilson@xxxxxxxxxx>
To:      
 eclipse-pmc@xxxxxxxxxxx
Date:      
 21.06.2016 16:10
Subject:    
   Re: [eclipse-pmc]
Update Release Rules
Sent by:    
   eclipse-pmc-bounces@xxxxxxxxxxx

---

In general it's fine. I do think we've always had some
level of "bug fixes" going on that went beyond purely things
that "increase stability", and I don't want us to sound like
we're trying to be *more* strict here. Personally, I feel like we should
acknowledge first that we do want new feature work, and then that we want
that to be done in keeping with our quality goals. Here's a variation:
" 
For the Eclipse top-level project, we recognize that the
pace of software development has increased to the point where feature work
can not be constrained to one release per year. However, the expectation
of the community is that our Update releases will provide increased stability
and overall improved quality. To ensure that we maintain these expectations,
feature work to be delivered into an Update release needs to be brought
forward to the PMC for approval, as is done for API changes (including
additions). Only fixes and features that have been already working fine
in master for some time can be brought forward. Having the work first in
master and tested by the community before it gets backported, is our normal
workflow. In addition, any backport needs to be reviewed by another committer.

"
What do you think?

McQ.

"Daniel Megert" ---2016/06/21 09:32:36---Hi PMC As discussed, here's the draft note I plan to send out regarding our rules

From: "Daniel Megert" <daniel_megert@xxxxxxxxxx>
To: "eclipse-pmc@xxxxxxxxxxx" <eclipse-pmc@xxxxxxxxxxx>
Date: 2016/06/21 09:32
Subject: [eclipse-pmc] Update Release Rules
Sent by: eclipse-pmc-bounces@xxxxxxxxxxx

---

Hi PMC

As discussed, here's the draft note I plan to send out regarding our rules
for Update Releases. Please approve or provide corrections.

For the Eclipse top-level project the main goal for Update releases is
still to increase stability. Therefore, like for API changes (including
additions), any feature work needs to be brought forward to the PMC for
approval. Only fixes and features that are already working fine in master
for some time can be brought forward. Having the work first in master and
tested by the community before it gets backported, is our normal workflow.
Also, any backport needs a review from another committer.

Dani
_______________________________________________
eclipse-pmc mailing list
eclipse-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/eclipse-pmc

[attachment "graycol.gif" deleted by Daniel Megert/Zurich/IBM]
_______________________________________________
eclipse-pmc mailing list
eclipse-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/eclipse-pmc