Add verbiage about expired SRE issues (#5543)

src/doc/dev_manual/SiteReliabilityEngineering.rst

@@ -12,7 +12,7 @@ Some of these may relate to the *use* of VisIt_ such as
 and some may relate to an *operational* aspect of either the VisIt_ software
 itself such as
 
-    * A botched *managed* VisIt installation.
+    * A botched *managed* VisIt_ installation.
     * An update to host profiles to address site access changes.
     * A missing database reader plugin.
 
@@ -251,13 +251,18 @@ Active SRE Issues Repo
 `issues-only repository <https://github.com/visit-dav/live-customer-response/issues>`_
 within the `visit-dav GitHub organization <https://github.com/visit-dav>`_. 
 For each new inquiry, the primary will file an issue ticket and assign themselves.
-When the inquiry is :ref:`resolved <sre_response_vs_resolution>`, the associated
-issue is closed. The primary will endeavor to capture all relevant information and
+
+The primary will endeavor to capture all relevant information and
 communications in this issue. The use of GitHub issues for this purpose has a number
 of advantages over other options such as email including better search/browse as well
 as support for attachments. For this reason, a number of steps were taken to integrate
 the ``visit-users@elist.ornl.gov`` email list with this issues-only repository.
 
+The SRE issue shall be closed when the associated inquiry is
+:ref:`resolved <sre_response_vs_resolution>`. Or, it will be closed and labeled
+``wontfix`` after 21 days pass since the user last engaged in any conversation with
+VisIt_ developers to reach a resolution.
+
 Upon receiving a *new* inquiry on the ``visit-users`` email list, telephone hotline
 call, or walk-in (with the exception of walk-ins involving classified information),
 the procedure is for the **Primary** to cut-n-paste the initial email to a new