理想情况下，它应该有一个名称，并且不应替换已存在的版本。Paratext 在启动项目进度时，应仅显示最新版本。不替换旧版本还意味着 Paratext 可以更轻松地将计划的任何先前版本自动更新到新版本（例如，如此视频中所示）。
项目计划开发人员的注意事项：
- 您应确保计划 ID 从一个版本到下一个版本没有改变。
- 您应确保所有阶段和任务的 ID 保持不变。
- 请确保在文件中设置了计划版本号。
- 理想情况下，您使用了 （按住 Shift 键）Paratext > Support and development > Base project plans 来创建新版本。如果您之前不知道这个功能的存在，现在可能已经太晚，无法再使用它了。
有关创建计划更新的更多信息，请参阅此帖子。
编辑：看起来名称不同对自动更新过程的重要性并不像我最初认为的那么大，而且版本号实际上会成为计划 ID 的一部分（因此它是 {ID}_{Version}）。
Ideally, it should have a name and should not replace the one that already exists. Paratext should only show the most recent version when starting progress for a project. Not replacing it also means that Paratext can more easily automatically update any previous version of the plan to the new version (e.g. as shown in this video).
Note for the developers of a project plan:
- You should ensure that the plan ID has not changed from one version to the next.
- You should ensure that the ID of all stages and tasks are the same.
- Make sure the plan version number is set in the file.
- Ideally, you used (Hold Shift) Paratext > Support and development > Base project plans to create the new version. If you didn’t know this existed, it is likely too late to work with it now.
See this post for more information on creating plan updates.
EDIT: It appears having a different name isn’t as important to the automatic update process as I originally thought and that the version number actually becomes part of the plan ID (so it’s {ID}_{Version}).
机器翻译自 English
