Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 543224

Summary:	[efsp][1.1] Revise the EFSP
Product:	Community	Reporter:	Wayne Beaton <wayne.beaton>
Component:	Process	Assignee:	Eclipse Management Organization <emo>
Status:	RESOLVED MOVED	QA Contact:
Severity:	normal
Priority:	P3	CC:	paul.buck, rmonson, tanja.obradovic
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Linux
URL:	https://github.com/EclipseFdn/EFSP/issues/2
Whiteboard:
Bug Depends on:	543471
Bug Blocks:

Description Wayne Beaton

2019-01-07 15:50:56 EST

Let's use this as a container, or umbrella bug to address updates to the Eclipse Foundation Specification Process. I'd like to make this a minor revision (so no structural changes).

For this first revision, I'd like to address the following:

* Add consideration of Maintenance Releases;
* An "Individual Participant" is defined in terms of an "individual Committer", but "individual Committer" is not defined;
* Ensure that it is clear that a "Member Participant" is a member of the Working Group; and
* Move "The Specification Project creation process" diagram to a supporting document (this diagram feels out of place here).

Is there anything else to address in this iteration?

Comment 1 Richard Monson-Haefel

2019-02-13 12:00:08 EST

I would recommend removing the following "may also be referred to as a Maintenance Release" as it confuses things especially later in the document when you use only the term "service" . I know why its there but I think we have to settle on "Service" or "Maintenance Release" but not both.

Comment 2 Richard Monson-Haefel

2019-02-13 12:04:50 EST

I would add something like this to the Service release definition to ensure that it limited to very minor changes.

"A Service Release does not include any significant new features and/or breaking changes"

Comment 3 Wayne Beaton

2019-02-20 14:13:52 EST

I've moved this discussion to https://github.com/EclipseFdn/EFSP/issues/2