Should we talk about release cycle today? We’re going to start pushing two types of changes 1. hotfixes 2. changes that should be added to next release. there are logistics we need to figure out around this, i.e. having release branches etc.

For now I'd prefer much more frequent master-based releases, almost no hotfixes (they'd just go towards the next release, and no release branches)

Basically http://scottchacon.com/2011/08/31/github-flow.html with occasional tagged releases

i’m worried about the cost of having to re-QA everything all the time.

i’m about to put up a PR to fix schema message validation.

before this goes in, we should pretty much test every integration again.

if we need to do this for every change in the core worker before we push to master or a feature branch we will never get anything done.

let’s discuss more in sync today!

my concern is probably just indicative that our integration testing is not good enough, because i don’t trust it.

Yeah, I'd prefer to focus on improving integration testing over modifying the release mechanism. Let's definitely discuss though.

Oh we didn't talk about this during the sync.

Want to talk about it next sync or set up something in the next couple hours @charles?

i’d be happy to discuss today.

i go on vacation tomorrow so not the next sync 😛

though it’s totally fine if you guys come up with a plan for this without me.