
\summary{2011}{11}{8}


\agendaitem{ChangeLog and commit messages}
\index{ChangeLog}

\vote{Do we require identical ChangeLog entries and commit
messages?}{The Council agreed that developers are free to use different messages
for ChangeLog and commit, but they are responsible for the messages,
and the Council still expects appropriate messages to be used.
--- \url{http://devmanual.gentoo.org/ebuild-writing/misc-files/changelog/}}


\agendaitem{Eclasses policy}
\index{eclasses!api changes}

\vote{Are developers allowed to remove functions from
eclasses, or change the API in general?}{
The Council agreed that the following wording shall be added to the
eclass writing guide in the devmanual:
\begin{quote}
   "When removing a function or changing the API of an eclass, make
   sure that it doesn't break any ebuilds in the tree, and post a
   notice to gentoo-dev at least 30 days in advance, preferably with
   a patch included."
\end{quote}}

Actions:
\begin{itemize}
\item Provide a patch for the devmanual (betelgeuse).
\item Start a discussion on the mailing lists on how to deal with eclass
  APIs in general (grobian).
\end{itemize}


\agendaitem{Open bugs with Council involvement}

\begin{itemize}
 \item 
 \bug{331987}: No progress since last month.
Action: Inform Infra about last month's Council decision (jmbsvicetto).
 \item
 \bug{341959}: No progress since last month.
Action: hwoarang will talk to tove and sort it out.
\end{itemize}


\agendaitem{Open floor}

No issues were brought up to the council by the community.
