Revert "RFC-666: Updates for butler and build setup"

lsst · Mar 8, 2020 · 6a970f6 · 6a970f6
1 parent 6a6db9c
commit 6a970f6
Show file tree

Hide file tree

Showing 9 changed files with 12 additions and 18 deletions.
diff --git a/.travis.yml b/.travis.yml
@@ -4,7 +4,7 @@ services:
    - docker
 language: python
 python:
-   - '3.6'
+   - '3.5'
 before_install:
    - "pip install 'lander>=0.1.0,<0.2'"
 install:

diff --git a/LDM-294.tex b/LDM-294.tex
@@ -1,4 +1,4 @@
-\documentclass[DM,toc]{lsstdoc}
+\documentclass[DM,lsstdraft,toc]{lsstdoc}
 
 \setDocChangeRecord{%
 \addtohist{1.1}{2004-06-23}{Initial version (Document-139).}{J.~Kantor}
@@ -16,14 +16,14 @@
 \addtohist{3.6}{2019-01-29}{Review product tree. Add release management subsection. Update DMCCB and DMSE team. Approved in \jira{RFC-561}}{G.~Comoretto}
 \addtohist{3.7}{2019-02-06}{Add text for LSP and Middleware mangers. Time allocation policy for institutional scientists, add admin names to org chart. Approved in \jira{RFC-572}}{W.~O'Mullane, L.~Guy}
 \addtohist{3.8}{2019-07-29}{Updates to Org charts, glossary, third party software, risk management, milestones. Approved in \jira{RFC-621}}{W.~O'Mullane, L.~Guy}
-\addtohist{3.9}{2020-03-07}{Update SST org chart, add Middleware and Science Platform teams, provide more details on responsibility for debugging builds and hosting releases. \jira{RFC-666}, \jira{DM-22393}}{W.~O'Mullane}
+\addtohist{}{2019-12-21}{SST org charts, middleware lead, builds and fixes  milestones. \jira{DM-22393}}{W.~O'Mullane}
 }
 
 \title[DM PMP]{Data Management Organization and Management}
 
 \author   {William O'Mullane, John Swinbank, Mario Juric, Leanne Guy and DMLT}
 \setDocRef      {LDM-294} % the reference code
-\setDocDate     {2020-03-07}              % the date of the issue
+\setDocDate     {\today}              % the date of the issue
 \setDocUpstreamLocation{\url{https://github.com/lsst/LDM-294}}
 
 %

diff --git a/dmgroups.tex b/dmgroups.tex
@@ -84,12 +84,7 @@ \subsection{DM Systems Engineering Team \label{sect:sysengt}}
 \item Agree the process for tracing the baseline requirements verification and validation status.
 \item Agree the formal versions of documents and software which form the technical baseline, individual items will go through the CCB for formal approval.  This includes upload to docushare.
 \item Perform releases of software products --- including, but not limited to, the Science Pipelines --- as needed, using tooling provided by SQuaRE (\secref{sect:square}).
-\item Debug unexpected build problems:
-\begin{itemize}
-  \item{Resolve issues related to the underlying build infrastructure directly;}
-  \item{Pass off product-specific problems to the relevant product team.}
-\end{itemize}
-\item Maintain the build/packaging system e.g.  newinstall.sh, lsstsw, lsst\_build.
+\item Debug build problems related tot he build infrastructure for any product being released --- pass off product specific problems to the relevant product time.
 \end{itemize}
 
 Some of these tasks are will be delegated to individual group members.
@@ -228,5 +223,5 @@ \subsection{Science Platform Team \label{sec:sciplat}}
 The Science Platform Team is responsible for delivering the three aspects of the LSST Science Platform, as described in \citeds{LDM-542}.
 
 The Product Owner for the Science Platform is the \gls{DMSS}, supported by the Science Platform Scientist (\secref{role:scip}).
-The team is managed by the Science Platform Manager (\secref{role:lsplead}).
+The team is managed by the Middleware Manager (\secref{role:mwlead}).
 They coordinate effort across the subsystem, drawing primarily on the Data Access Services (\secref{sect:dax}), Data Facility (\secref{sect:ldf}) and SQuaRE (\secref{sect:square}) teams.
diff --git a/dmroles.tex b/dmroles.tex
@@ -103,8 +103,7 @@ \subsection{Senior Advisor / Pipelines Scientist \label{role:pipe}}
 \subsection{Science Platform Scientist \label{role:scip}}
 The Science Platform is composed of three aspects. Each aspect is produced in a different institution.
 Each aspect has its own science lead/product owner.
-The product owner for the Platform is the \gls{DMSS} \secref{role:dmps}, who has final say on requirements and features.
-However, since the Platform is a vital tool for \gls{LSST} science we feel it is also important to have a scientist considering the platform as a whole.
+The product owner for the Platform is the \gls{DMSS} \secref{role:dmps}; who has final say on requirements and features; however since this is a vital tool for \gls{LSST} science we feel it is also important to have a scientist considering the platform as a whole.
 Hence this role is to be the scientific guardian of the science platform as a whole, to make sure all of the aspects work together in a useful manner allowing scientific exploitation of the \gls{LSST} data. The \gls{Science Platform} Scientist works in close collaboration with the \gls{DMSS}.
 
 \subsection{Systems Engineer \label{role:sysengineer}}

diff --git a/images b/images
diff --git a/intro.tex b/intro.tex
@@ -21,6 +21,7 @@ \subsection{Goals and Objectives}
 \end{itemize}
 
 The DM goals in selecting and, where necessary, developing LSST software solutions are:
+
 \begin{itemize}
 	\item Acquire and/or develop solutions: To achieve its mission, LSST DM prefers to acquire and configure existing, off-the-shelf, solutions. Where no satisfactory off-the-shelf solutions are available, DM develops the software and hardware systems necessary to:
 \begin{itemize}

diff --git a/leadtutes.tex b/leadtutes.tex
@@ -19,9 +19,9 @@ \subsubsection{Science Quality and Reliability Engineering \label{sect:square}}
 
 \item \gls{DM} documentation support, to include defining standards and providing tooling for documentation as well as some document writing
 
-\item Development and support of the build infrastructure (e.g. Jenkins,  groovy and dm-jenkins-jobs ) and release tools (e.g. container creation) for all \gls{DM} software products
+\item Development and support of the build infrastructure (e.g. Jenkins) and release tools (e.g. container creation) for all \gls{DM} software products
 
-\item Deploy, host and manage repositories of release artifacts, such as private Conda repositories, to support releases as needed and agreed with the Systems Engineering Team (\secref{sect:sysengt})
+\item Provide repositories of release artifacts, such as private Conda repositories, to support releases as needed and agreed with the Systems Engineering Team (\secref{sect:sysengt})
 
 \end{itemize}
 

diff --git a/lsst-texmf b/lsst-texmf
diff --git a/skipacronyms.txt b/skipacronyms.txt
@@ -10,4 +10,3 @@ SE
 WOM
 XYZ
 GIT
-USA