Introduction

At a high level, promoting code into production works as follows:

Only promote next into production

All code to go into production should be in the next branch

Preparation

1. Conduct regression Testing

2. Update docassemble package metadata (in setup.py in setup()). Check the following:

   1. name - should match repository name (Note: the name may not match if the repository has been provisioned according to the Provisioning a New Docassemble Repository standard
   2. version number - use x.y versioning. Promoter's call as to which version number to increment
   3. description - make sure it's meaningfulr
   4. long_description
   5. author_email (should be [email protected]) (TBC)
   6. licence - should be `Copyright (c) YYYY Flinders University. All Rights Reserved'
   7. url - should be https://flinders.edu.au

3. Review README.md. Make sure it makes sense

4. TBC Update changelog

Promotion

1. Raise pull request TBC