[ https://ovirt-jira.atlassian.net/browse/OVIRT-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
eyal edri [Administrator] reassigned OVIRT-20: ---------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Document oVirt infra SLA > ------------------------- > > Key: OVIRT-20 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-20 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: General > Reporter: quaid > Assignee: Evgheni Dereveanchin > Priority: Highest > > We need to document how we make changes: > * What services need notices out to the world? > * What are the timeframes for notices? > \\- 1 hour for critical > \\- 12 to 24 hours for non-critical > * Who needs to be notified for what? > \\- e.g. leave announce out of administrivia > \\- arch, users, and infra are the defaults so far > \\- perhaps create an infra-announce list that just includes the others? > * When do we not make changes? > \\- change freeze around releases > \\- other change freeze reasons > * What is the process to make a change during a freeze? > \\- When is the freeze slushy? > \\- When is the freeze solid and should not be broken because of the > potential risk at that moment? (We need something to weigh risk against risk.) -- This message was sent by Atlassian JIRA (v1000.621.5#100023) _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra