table1.html

<link rel="stylesheet" href="_static/css/fe-table.css" type="text/css" />
<table class="fe-table">
<thead>
<tr>
<th>Service Instance</th>
<th>Bleed</th>
<th>Dev</th>
<th>Int</th>
<th>Prod</th>
</tr>
</thead>
<tbody>
<tr> <!-- CLOUD ENVS -->
<td>Science Platform - Science Deployments (IDF, LDF, USDF)</td>
<td>Automatic</td>
<td>Developer-at-will, no heads-up required</td>
<td><code>#rsp-team</code> channel announcement, courtesy 1hr notice</td>
<td>Release manager has to okay on <code>#rsp-team</code>, 24 hour notice minimum</td>
</tr>
<tr> <!-- TELESCOPE ENVS -->
<td>Science Platform - Telescope Deployments(summit, base, NTS)</td>
<td>N/A</td>
<td>For SQuaRE services typically in maintenance window</td>
<td><code>For SQuaRE services, in maintenance window</td>
<td><code>#square-summit-support</code> details, <code>#summit-announce</code> start/end of maintenance window</td>
</tr>
<tr> <!-- ROUNDTABLE -->
<td>Roundtable (LSST-the-docs and other non-data services), SQuaSH</td>
<td>N/A</td>
<td>Developer-at-will, no heads-up required</td>
<td>N/A</td>
<td>If service disruption is expected, in maintenance window, notice in relevant service channels (<code>#square-docs-support</code>, etc), otherwise SQuaRE self-co-ordinates.</td>
</tr>
<tr> <!-- CLO ETC -->
<td>community.lsst.org</td>
<td>N/A</td>
<td>N/A</td>
<td>N/A</td>
<td>If service disruption is expected, scheduled in co-ordination with<code>#community-science-team</code>. Otherwise in maintenance window.</td>
</tr>
</tbody>
</table>