Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change Process Guidelines #684

Draft
wants to merge 7 commits into
base: working_draft
Choose a base branch
from
14 changes: 14 additions & 0 deletions SPEC-CHANGE-GUIDLINES.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,6 +23,20 @@ A changelog is provided specifying helpful information to consumers of focus dat

TODO: A series of guidelines of how changes are proposed, reviewed, and accepted.

### Addition of a New Feature or Column

When a new feature or column is introduced to the FOCUS specification, depending on the circumstances of the change, the support of the column may be initially optional. This is to allow for the adoption of a new feature or columne by prodivers that support it, without restricting other adopters from using newer versions of the specification.
- The feature or item addition is proposed, which, in addition to the proposed specification change, includes the appropriate indication as to the optionality of the feature or column. ??Do we require a future optionality is solidified version??
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removal indication of optionality just say it is a new thing.

- example: "Example Column 1 will be deprecated in version 2.1 and removed in version 2.4"


### Removal of a Feature or Column

When a feature or column is removed from the FOCUS specification, the following steps are taken:
- The feature or item removal is proposed, which, in addition to the proposed specification change, includes a deprecation period expressed in terms of Focus versions
- example: "Example Column 1 will be deprecated in version 2.1 and removed in version 2.4"



## Change Type Classification

Expand Down