https://linen.dev logo
#contributing-to-airbyte
Title
# contributing-to-airbyte
c

charles

09/24/2020, 5:03 PM
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.
u

user

09/24/2020, 5:12 PM
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)
u

user

09/24/2020, 5:12 PM
Basically http://scottchacon.com/2011/08/31/github-flow.html with occasional tagged releases
u

user

09/24/2020, 5:15 PM
i’m worried about the cost of having to re-QA everything all the time.
u

user

09/24/2020, 5:15 PM
i’m about to put up a PR to fix schema message validation.
u

user

09/24/2020, 5:15 PM
before this goes in, we should pretty much test every integration again.
u

user

09/24/2020, 5:16 PM
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.
u

user

09/24/2020, 5:16 PM
let’s discuss more in sync today!
u

user

09/24/2020, 5:17 PM
my concern is probably just indicative that our integration testing is not good enough, because i don’t trust it.
u

user

09/24/2020, 5:18 PM
Yeah, I'd prefer to focus on improving integration testing over modifying the release mechanism. Let's definitely discuss though.
u

user

09/24/2020, 9:47 PM
Oh we didn't talk about this during the sync.
u

user

09/24/2020, 9:47 PM
Want to talk about it next sync or set up something in the next couple hours @charles?
u

user

09/24/2020, 9:57 PM
i’d be happy to discuss today.
u

user

09/24/2020, 9:57 PM
i go on vacation tomorrow so not the next sync 😛
u

user

09/24/2020, 9:57 PM
though it’s totally fine if you guys come up with a plan for this without me.