docs: add seata versions maintain plan docs #740
Conversation
|
|
||
| （上图为Apache Seata(incubating)历史版本维护的状态图） | ||
|
|
||
| 需要注意的是，社区仅维护当前时间点下最新的3个版本，并且对于非当前版本，只提供安全漏洞和bugfix相关的迭代，鼓励用户尝试最新版本的feature并给出反馈。 |
There was a problem hiding this comment.
How is the period calculated on the picture here, and why does 1.7 have a 6 month maintenance period and 1.8 only 3 months?
There was a problem hiding this comment.
How is the period calculated on the picture here, and why does 1.7 have a 6 month maintenance period and 1.8 only 3 months?
This is calculated through the time node of the community release. Our maintenance time is until the release of the next official version, so the span of 1.7 is very large.
There was a problem hiding this comment.
Based on the release dates, considering that version 1.6.0 was released in December, and version 1.7.0 was released in the following July, the period between these releases is considered the stability maintenance period for version 1.6.0. With version 1.8.0 being released in October, the stability maintenance period for version 1.7.0 is between July and October.
What is the purpose of the change
add seata versions maintain plan docs
Brief changelog
add seata versions maintain plan docs
Follow this checklist to help us incorporate your contribution quickly and easily:
doc: add an operations guide document. Each commit within the pull request should contain a meaningful subject line and body.npm run build, and make sure it works as expected.buildfolder are included in the commit, as well as thepackage-lock.jsonandyarn.lockfiles.