Hi folks,

Since this has been brought up a few times on various tickets I thought now
would be a good time to go over our project workflow and make sure it's
working for us.

A general overview of the workflow that we use is available at [1]. A brief
overview is that:
- ALL changes are pushed up to Github for code review before being merged.
- If no issues are raised within a reasonable amount of time (usually 72
hours is what I stick with) those changes can be merged.

In general, I've been quite happy with this workflow. We have a low enough
throughput that this isn't overwhelming and I think it's great that we can
get together and review each other's code. I know I appreciate the
opportunity for people to find issues with my code before we merge it. I
think it would be beneficial to flesh out the docs a bit more on the
workflow (for instance, how to run tests should be included in there, how
long to wait for a merge, etc.). So community, what do we think of our
workflow? Do we like it so far? Is it working for us? Are there pain
points? What don't we like? Etc.

[1]
https://cwiki.apache.org/confluence/display/CLIMATE/Developer+Getting+Started+Guide


-- Jimmy

Reply via email to