Meetings 2017 04 20

April 20, 2017

release cadence/intervals
- monthly patch/non-breaking releases
  - includes simple PRs, bug fixes, etc to avoid issues becoming stale and encourage community contribution
  - new releases on Tuesday evening
- progressive monthly releases, as features are ready for release
  - how can we use release candidates to test out new features with the community?
    - merge develop into release branch 1 week prior to release
    - develop merges can continue, but our focus is prepping the release for master
    - have wiki page to onboard new RC testers (e.g. link to Steve's repo-tool)
    - each go package (revel, cmd, modules, etc) would have a synced release branch
dependency management
- gopkg.in support
  - it's been discussed before in 2014
  - could add complexity
- https://github.com/golang/dep
automating the release cycle
- codifying the steps in the spirit of DevOps
- so releases can happen without us
- running CI, exporting docs, posting announcement to social media, etc
- Shawn will research options and we'll review and decide as a team later
workflow tooling
- waffle.io
  - good for issues and PRs
  - can filter by milestone across all repos
    - shows GH activity across all repos to stay on top of new, incoming activity
  - uses tags to sort issues into columns
    - Steve sync up waffle's labels to match our defined workflow GH labels (waffle-COLUMN)
- GH projects
  - good for planning new features

Development

Resources

Community