summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
Diffstat (limited to 'decisions/summary-20170611.tex')
-rw-r--r--decisions/summary-20170611.tex33
1 files changed, 33 insertions, 0 deletions
diff --git a/decisions/summary-20170611.tex b/decisions/summary-20170611.tex
new file mode 100644
index 0000000..6b157d2
--- /dev/null
+++ b/decisions/summary-20170611.tex
@@ -0,0 +1,33 @@
+
+\summary{2017}{6}{11}
+
+Agenda call: \agoref{gentoo-project}{311aa9019263ee4e4ef68300ce3e4a46}
+
+Agenda announcement: --- none ---
+
+\agendaitem{Open bugs with council involvement}
+\index{project!qa}
+
+\begin{itemize}
+ \item
+ \bug{618930}: \dev{pinkbyte} was confirmed as QA lead with 5 yes votes and 2
+ abstentions.
+ \item
+ \bug{618254}: (Non-public discussion.)
+\end{itemize}
+
+\agendaitem{Open floor}
+\index{bugzilla!package list}\index{stabilization}\index{developer!jer}
+
+\dev{soap} brought up the topic of the stabilization workflow and the new
+package list field in bugzilla. Specifically he asked for votes on two topics,
+\begin{itemize}
+ \item
+ that the package maintainer is responsible for initiating stabilization, i.e.,
+ if stabilization is requested by someone else the maintainer has to confirm
+ \item
+ that only the package maintainer is allowed to modify the package list field
+\end{itemize}
+As a result also a discussion on specifying the package list format ensued. No
+vote was taken; the topic was deferred to the lists for decision at the next
+meeting.