search

unee-t / bugzilla-customisation

Unee-T's customisation on top of Bugzilla
https://hub.docker.com/r/uneet/bugzilla-customisation/
GNU Affero General Public License v3.0
5 stars 7 forks source link

Unclear process to release in production #70

Closed franck-boullier closed 5 years ago

franck-boullier commented 6 years ago

What is the process to release this in the production environment?

kaihendry commented 6 years ago

Production deployments are triggered on tagged releases like the frontend.

This is codified by "tags: true" in https://github.com/unee-t/bugzilla-customisation/blob/master/.travis.yml

franck-boullier commented 6 years ago

@kaihendry the mechanism is clear (tagging) but the process is not:

kaihendry commented 6 years ago

We tag when we want to make a release to customers. Criteria ultimately should be not to cause a bad UX for the customer. i.e. be aware of any dependencies / migrations and anything that can break things. And to do it as often as possible. Fast production development cycles are especially important at this stage. Solicit feedback from users when a new feature is pushed.

A "release manager", I was assuming it was you, makes that call. In previous roles as a release manager, I review the commits, and conduct my own testing before rubber stamping the release, since I am responsible.

To make life easier, I would employ UIlicious to create tests on flows we care about. But things like adding a form control https://github.com/unee-t/frontend/issues/405 can break things. https://media.dev.unee-t.com/2018-07-24/uilicious.mp4

franck-boullier commented 6 years ago

Pending: Document the release process (in the ReadMe?) and make sure people in charge know what they have to.