codewalker/marked
1
0
Fork 0
Code Pull Requests Actions Packages Releases Activity

Remove details

Browse Source
This commit is contained in:
Josh Bruce 2018-04-25 08:33:13 -04:00
parent cbdc4f071e
commit b57518d9a5
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/PUBLISHING.md
View File

@ -20,5 +20,5 @@ We follow [semantic versioning](https://semver.org) where the following sequence
What to expect while Marked is a zero-major (0.x.y): What to expect while Marked is a zero-major (0.x.y):
1. The major will remain at zero; thereby, alerting consumers to the potentially volatile nature of the package. 1. The major will remain at zero; thereby, alerting consumers to the potentially volatile nature of the package.
2. The minor will tend to be more analagous to a `major` release. For example, we plan to release `0.4.0` once we have fixed most, if not all, known issues related to the CommonMark and GFM specifications because the architecture changes planned during `0.4.0` will most likely introduce breaking changes. 2. The minor will tend to be more analagous to a `major` release.
3. The patch will tend to be more analagous to a `minor` release. 3. The patch will tend to be more analagous to a `minor` release or a collection of bug fixes (patches).