Updating and sharing base plans

Question

My organization has created and submitted a custom base plan (1.0) that now ships with PT. I’ve recently updated it on my computer to version (1.3). I’d like to train on it next week tweak it further (1.4) as a result of discussions, and then submit it for release with the next version of PT. In the meantime, can I share it manually with my teammates who are working on different projects by replacing their 1.0 XML in the _standardplans folder on the project administrators’ computers?
Is there another way to go about this that I don’t know about?
Thanks for your help!
Regards,
Fork

Answer 1

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}).