Editing Software Engineering (Winter 2026) (section)

==== Bot Project Task #6 ====
;Task: Release version 2.0
;Due: February 27 (Friday), 11:59 p.m. Seattle time.
;Deliverables: You are done with Task 6 if you have each completed at least one very large or three small user stories from your second sprint and deployed version 2 to your production environment for Professor Champion to review. Note the rubric on Canvas for this. Tag the code so that it is clear which version is 2.0. See list of steps for all the items you'll be graded on.
;Turn in: A screenshot of version 2.0 of your bot in action with comments and links to your work, as well as reflections (see rubric) 

'''Steps'''
# In sprint planning, assign user stories to each member of the group. Note the rubric on Canvas for this task.
# During the sprint, resolve user stories. User stories should be well-formed: assigned, estimated, with specifications: inputs, outputs, acceptance criteria. Link them to the pull request. 
# Commit often! Test often! Make sure your commit messages make sense.
# Open a pull request to merge your feature branch into the team's main branch.
# Review your pull requests for conflicts.
# Include an up-to-date SBOM with your release in a standards-compliant format.
# Merge code and tag a release when done with the sprint scope.
# Deploy your version 2.0 into the production environment.
# Update your Kanban board and issue release notes.
# Repository must be clean and clear. If you have files from previous releases, they should be clearly marked.

;Tips:
* Feel free to use AI tools as a tutor or source for debugging any issues that come up.
* Be disciplined in your use of GitHub: use feature branches, pull requests, link pull requests and the user stories they resolve.
* Clean up your own messes: don't expect others to fix your conflicts.