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.

Sign up for GitHub

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

Feature/semver strategy #615

Merged
merged 1 commit into from
Aug 21, 2016
Merged

Feature/semver strategy #615

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,8 +7,9 @@
* Move unsorted rules into their respective sections.
* Update the `summary` style in all browsers.
* Remove `::placeholder` styles due to a bug in Edge.
* More explicitly define font resets on form controls
* Remove the `optgroup` normalization needed by the previous font reset
* More explicitly define font resets on form controls.
* Remove the `optgroup` normalization needed by the previous font reset.
* Update the semver strategy.

### 4.2.0 (June 30, 2016)

Expand Down
13 changes: 9 additions & 4 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -196,7 +196,12 @@ cutting new releases.
version numbers are incremented in a project. Versions are written as
MAJOR.MINOR.PATCH.

Changes limited to fallback declarations for browsers which do not support
newer features produce a PATCH release.

Changes limited to normalizations for older browsers produce a MINOR release.
Any change to CSS rules whatsoever is considered backwards-breaking and will
result in a new **major** release. Others changes with no impact on rendering
are considered backwards-compatible and will result in a new **patch** release.

No changes to CSS rules can add functionality in a backwards-compatible manner,
therefore no changes are considered **minor**. For instance, a normalization on
an element selector may override a user style on a universal selector, a
change to `opacity` might cause [inputs to disappear](https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/3901363/),
or a change to `background-color` might cause [backgrounds to shrink](https://github.com/jonathantneal/sanitize.css/issues/42).