beautifier/js-beautify

Review version numbering policies

Open

#1,257 opened on 2017年9月18日

GitHub で見る
 (2 comments) (0 reactions) (0 assignees)JavaScript (8,342 stars) (1,460 forks)batch import
help wantedtype: discussiontype: task

説明

This project is extremely popular and as such needs to be stable, solid, and more conservative in versioning and changes.

We've been using semantic versioning reasonably accurately. There have been no breaks to backward compatibility in sometime, and the most changes are bug fixes.

However, semver only encodes intentional breaking changes, it doesn't address potentially risky changes. We should consider a change's risk of causing breakage in our version numbers.

Also, many projects do not not lock or even limit their version dependencies. Those that do often use ^x.y.z instead of ~x.y.z, which would mean they take updates when y or z change.

Consider switching to making major version updates under more circumstances to limit risk to dependent projects.

コントリビューターガイド

Review version numbering policies · beautifier/js-beautify#1257 | Good First Issue