Deployments: Principles for deploying changes

canonical-web-and-design / practices

Guides and principles from the web team at Canonical and Ubuntu

https://canonical-web-and-design.github.io/practices/

Other

44 stars 30 forks source link

Deployments: Principles for deploying changes #89

Closed nottrobin closed 6 years ago

nottrobin commented 6 years ago

Start a document to explain some important princilpes around when to release changes to our projects:

Master branch is always releasable (this has been a principle for years, but I'm finally writing it down)
No risky releases on a Friday (this is new, and came out of https://portal.admin.canonical.com/C113582/)

barrymcgee commented 6 years ago

LGTM 👍🏻

deadlight commented 6 years ago

Formal clarification of releasable master rule :+1:

Cautious Fridays (like Casual Fridays but different) :+1:

anthonydillon commented 6 years ago

:+1:

nottrobin commented 6 years ago

Fixes https://github.com/ubuntudesign/base-squad/issues/133

nottrobin commented 6 years ago

Since filing this, I realised there was already a deploy.md, and decided it would be a little neater to add to that instead of creating a new document. Please take another look and check you're happy with this new structure?

anthonydillon commented 6 years ago

Still :+1:

deadlight commented 6 years ago

👍

tbille commented 6 years ago

still :+1: