|Re: [eclipse-pmc] Update Release Rules|
+1 for Mike’s version, this is spot-on IMO.
Martin Oberhuber, SMTS / Product Owner – Development Tools, Wind River
direct +43.662.457915.85 fax +43.662.457915.6
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.
Back to the top