版本控制

🌐 Versioning

Ionic 框架遵循 语义化版本控制 (SemVer) 约定：主版本.次版本.修订号。不兼容的 API 更改会增加主版本，添加向后兼容的功能会增加次版本，向后兼容的错误修复会增加修订号。

发布时间表

🌐 Release Schedule

主要版本

🌐 Major Release

当 API 引入破坏性更改时，将发布一个主要版本。主要版本大约每 6 个月 发布一次，并且可能包含破坏性更改。在主要版本发布之前，将发布几个候选版本，以便在最终发布前获取反馈。发布候选版本时将包含更改内容及原因的概述。

🌐 A major release will be published when there is a breaking change introduced in the API. Major releases will occur roughly every 6 months and may contain breaking changes. Several release candidates will be published prior to a major release in order to get feedback before the final release. An outline of what is changing and why will be included with the release candidates.

次要版本

🌐 Minor Release

当添加新功能或引入非破坏性的 API 更改时，将发布次要版本。我们会对任何更改进行严格测试，以确保对发布充满信心，但新的代码可能带来新的问题。我们计划每 4 周 发布一次次要版本，如果进行了任何功能或 API 更改。

🌐 A minor release will be published when a new feature is added or API changes that are non-breaking are introduced. We will heavily test any changes so that we are confident with the release, but with new code comes the potential for new issues. We are scheduled to release a minor version every 4 weeks, if any features or API changes were made.

补丁发布

🌐 Patch Release

当包含错误修复但 API 没有更改且未引入破坏性更改时，将发布补丁版本。我们计划每周发布一个新的补丁版本，但有时可能需要比计划的时间更早或更晚发布。为了确保补丁版本可以修复现有代码而不会因新功能引入新问题，补丁版本将始终在小版本发布之前发布。

🌐 A patch release will be published when bug fixes were included, but the API has not changed and no breaking changes were introduced. We are scheduled to release a new patch version every week, but there may be times where we need to release sooner or later than scheduled. To ensure patch releases can fix existing code without introducing new issues from the new features, patch releases will always be published prior to a minor release.

更新日志

🌐 Changelog

要查看所有 Ionic 的显著更改，请参阅 更新日志。其中包含每个版本下所有错误修复和新功能的有序列表。