formalize development workflow and release cadence

[mbwatson]

• bi-weekly release cadence - every other Friday, staging -> master
• everything staged on day before release for acceptance testing
• develop branch (pre-staging) deployment?
  • potentially inside vpn, or just pw protected
• consider mid-sprint checkin meetings w devs/acceptance testers/stakeholders

[suejinkim20]

we will need to make a distinction between minor content changes and more complex functional code changes.

• for minor content changes, the current workflow is that content requests are submitted via the renci comms services request form and addressed via branches tagged /content/date the timeline for these requests is more fluid and are generally prioritized to be completed within 2-3 days
• bugs, features, and other updates are tracked through github issues and would follow the above cadence