Update Process

User Extended Update Process

Phase 1

• Remove unneeded commented code
• Add TODOs where needed
• Add comments to functions which still require it
• Cleanup formatting of files
• Change version numbering in comments and source. Add a final version to versions.yaml

Phase 2

• Test each feature according to the Testing Procedure
• Fix bugs as needed
• Feature freeze

Phase 3

• Update documentation to reflect changes
• Turn off 'Debug' in general.js
• Do a sweep of all assets to ensure they are clean and unnecessary code and files are removed
• Ensure images and and asset libs have been minified
• Sweep each source file for code formatting, incorrect comments, and commented out code which can be fixed or removed

Phase 4

• Test each feature according to the Testing Procedure
• Fix bugs as needed
• Repeat phase 4 until no further bugs are found

Phase 5

• Adjust October documentation and versioning
• Merge the update branch to the master branch
• Trigger the update on October's side
• Create a new branch based on the master branch for the next update
• Mark new deprecated functions/classes
• Comment out previously deprecated functions/classes
• Delete previously commented out functions/classes

Update Guide Version: v0.01