V1 End of support / V1 停止支持

[Mister-Hope]

VuePress V1 is old enough with a huge number of old deps, and has a few vulnerable secruity ptoblems. Also, it has some defects with design, it's poor at scalability, and has possible memory leak during built stage.

So, as VuePress V2 and VuePress Theme Hope V2 are both stable enough to be used in production, we are happy to announce that starting from 2022 March, V2 is the primary recommandation.

Meanwhile, it means that V1 will no longer have any development plan. All feature request and bug fixes are being dropped now.

• Any feature request on V1 will be marked with "won't fix" and closed
• Any bug report on V1 is still welcomed, but we will only investigate to make sure it's a bug and have it marked, but we will probably leave it if:
  • It's not stopping the whole dev or build process
  • V2 does not having similar issue

But don't be so worry, we still have limit support for V1:

• We still guarantee the basic function of V1, so if there are some breaking changes comming from VuePress@v1 or other deps, we will make sure that you will be able to use it to preview and build with it. (But small issues will be left there as mentioned above)
• Security problem which can be fixed will still be avialable in V1 untill 2023, which means we will take actions to upgrade our deps to a non-vulnerable version if possible
• PRs about new features and bug fixes are still welcome, if you managed to build something new or fix something incorrect, we are happy to merge it and bring you a new V1 version for it.

---

VuePress V1 已经足够老了，它拥有有大量的老旧依赖，并且有一些易受攻击的安全问题。此外，它在设计上存在一些缺陷，可扩展性较差，并且在构建阶段可能存在内存泄漏。

因此，由于 VuePress V2 和 VuePress Theme Hope V2 都足够稳定，可以在生产中使用，我们很高兴地宣布，从 2022 年 3 月开始，V2 将会被作为首选建议。

同时，也意味着V1将不再有任何开发计划，并停止所有新功能开发与错误修复。

• V1 上的任何功能请求都将标记为“won't fix”并关闭
• 我们永远欢迎任何关于 V1 的错误报告，但我们只会进行调查以确保它是一个错误并进行标记。如果出现以下情况，我们可能会忽视它：
  • 它不会停止整个开发或构建过程
  • V2 没有类似问题

不过不用担心，我们仍然对 V1 提供有限支持：

• 我们仍然保证 V1 的基本功能，所以如果有来自 VuePress@v1 或其他依赖的一些重大更改，我们将确保您能够使用它进行预览和构建。 （但是上面提到的小问题会留在那里）
• 可以修复的安全问题在 2023 年之前仍将在 V1 中可用，这意味着我们将采取措施尽可能将我们的依赖升级到非易受攻击的版本
• 我们永远欢迎有关新功能和错误修复的 PR，如果您设法构建新内容或修复错误内容，我们很乐意将其合并并为您带来新的 V1 版本。