This repository has been archived by the owner on Mar 24, 2023. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 4
/
CHANGELOG
56 lines (45 loc) · 3.59 KB
/
CHANGELOG
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
# ChangeLog
## [Version 1.3] - 2021-10-27
### Added
- Reference Patent Licenses, see https://github.com/EclipseFdn/EFSP/issues/47 and https://github.com/EclipseFdn/EFSP/issues/51
- Describe the relation between specification projects and working groups, see https://github.com/EclipseFdn/EFSP/issues/56
- The Eclipse Foundation Executive Director must approval all Project Proposals, see https://github.com/EclipseFdn/EFSP/issues/62
- Add clarification that the TCK must be licensed under the Eclipse Foundation TCK License https://github.com/EclipseFdn/EFSP/issues/65
### Removed
- Removes requirements regarding optional elements and supersetting (delegates to working groups), see https://github.com/EclipseFdn/EFSP/issues/42
### Changes
- The EFSP delivers Final Specifications not Specification Versions, see https://github.com/EclipseFdn/EFSP/issues/57
- Compatible Implementations must be based on a Final Specification, see https://github.com/EclipseFdn/EFSP/issues/45
- Clarify the definitions of Individual Participant and Member Participant to indicate agreement to actively participate in the Working Group and meet the requirements for participation as defined by the Working Group Charter.
- Clarify that a participant representative is a committer, see https://github.com/EclipseFdn/EFSP/issues/34
- Clarify the conditions by which a Participant Representative may be appointed, see https://github.com/EclipseFdn/EFSP/issues/23
- Remove Service Releases from the Approvals section of EFSP, see https://github.com/EclipseFdn/EFSP/issues/29
- A specification project may also be "created" by Restructuring Review, see https://github.com/EclipseFdn/EFSP/issues/11 and https://github.com/EclipseFdn/EFSP/issues/40
- TCK is "software and/or documentation", see https://github.com/EclipseFdn/EFSP/issues/49
## [Version 1.2] - 2019-06-30
### Added
- Clarification that all reviews are by default seven (7) days, see https://github.com/EclipseFdn/EFSP/issues/14.
- A section that describes how exceptions to the process may be granted, see https://github.com/EclipseFdn/EFSP/issues/12.
### Changes
- Clarified that there must be exactly one TCK (not "TCK project") for each Specification Version.
- The requirement to engage in Progress Reviews is now time-based, see https://github.com/EclipseFdn/EFSP/issues/13.
- Reworded parts of the "Specification Version Lifecycle" section.
- Clarify that a formal Release Cycle is not required for a Service Release.
- Clarified that a Progress Review must not overlap with a Release Review.
- Recasted the defined term "Milestone" as "Milestone Build".
## [Version 1.1] - 2019-03-20
### Added
- Link to the Eclipse Foundation Specification License.
- Link to the Eclipse Foundation TCK License.
- Definitions of "Release", "Major Release", and "Minor Release".
- Service Releases require a Release Review.
- Specification Committee votes requires a Super-major of members of the Working Group (not members of the Eclipse Foundation).
- Specification Committee votes must be scheduled to run for a period of no less than one week.
- All artifacts related to a vote must be delivered in distribution form to the Specification Committee prior to the start of the vote, must not change during the voting period, and must persist in the delivered form following the vote as part of the public record.
- New section that describes releases.
### Removed
- The Specification Project creation process diagram (moved to the FAQ).
### Changes
- Simplified the definition of "Service Release".
- Made the delivery of Final Specifications inclusive of Service Releases.
- Use the term "ballot" rather than the ambiguous "vote".