mirrors
/
freecol
mirror of https://github.com/FreeCol/freecol.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

More release doco revision.

This commit is contained in:
Mike Pope 2015-03-08 14:15:17 +10:30
parent 639afbc527
commit bec6e4e3f5
1 changed files with 21 additions and 20 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

41
doc/developer.tex
View File

@ -349,7 +349,7 @@ need \texttt{htlatex}, and \texttt{pdflatex} for the print manual.
You can avoid these requirements by setting the ant properties
\texttt{online.manual.is.up.to.date} and
\texttt{print.manual.is.up.to.date} respectively, however this is not
recommended for a release.
recommended for a release. Uploads to sourceforge use \texttt{sftp}.
\begin{itemize}
@ -379,7 +379,7 @@ recommended for a release.
\item Call \verb+ant dist+ in order to build all packages. You will be
prompted for the version of this release. Alternatively, you can
specify the version on the command line, by saying something like
specify the version on the command line, by with something like:
\begin{verbatim}ant -Dfreecol.version=0.9.0-alpha2 dist
\end{verbatim}
instead (replace 0.9.0-alpha2 with the correct version, of
@ -425,8 +425,10 @@ FILE
messages.
\item The \texttt{freecol.org} website is in transition to a new
format. For now, you will need to edit the \texttt{index.html},
format. For now, you will need to change the \texttt{index.html},
\texttt{news/index.html} and \texttt{download.html} files by hand.
Use \texttt{sftp} to log in at \emph{username}\texttt{,freecol@web.sf.net}
to upload changes.
%\item Update the release number in the "Version"-mambot at
% \texttt{http://www.freecol.org/administrator} > Mambots > Site Mambots > Version.
@ -444,14 +446,27 @@ FILE
\item Post release messages on our mailing lists: developers,
translators and users. Beware that you may have to be subscribed to
some lists to be able to post.The addresses are:
\texttt{freecol-{developers,translators,users}@lists.sourceforge.net}
some lists to be able to post. The addresses are:
\texttt{freecol-\{developers,translators,users\}@lists.sourceforge.net}
\item Post a release message to the FreeCol
\href{https://sourceforge.net/p/freecol/discussion/141200/}{forum}.
\item Post a news item on the FreeCol project \href{https://sourceforge.net/p/freecol/news/}{news} page on sourceforge.
\item Go to the bug tracker and create a new milestone (``Edit
Milestones'') called ``Fixed\_\emph{release}''
(e.g. ``Fixed\_0.10.2''). Select the ``Fixed\_trunk'' group and do
a mass edit (the pencil icon in the top right of the bug tracker
list) and move all bugs to the new milestone.
\item Do the corresponding action in other ticket categories that
have distinct release milestones.
\item Consider revising the preamble to the ``Bugs'' page,
particularly the ``Known Common Problems'' section. Go to Admin /
Tools / Bugs / Options to make changes.
\item Regenerate the documentation (with \verb+ant manual+) and
JavaDoc (with \verb+ant javadoc+) and update JavaDoc and User
Documentation on \href{freecol.org}{freecol.org}. You can do that
@ -475,21 +490,7 @@ cd doc
\end{verbatim}
%% Omitting the following for now. It will need to be revised if we
%% start doing unstable releases again.
%
%The following items can be omitted for unstable releases:
%
%\begin{itemize}
%
%\item Go to the bug tracker and create a new milestone (``Edit
% Milestones'') called ``Fixed\_\emph{release}''
% (e.g. ``Fixed\_0.10.2''). Select the ``Fixed\_trunk'' group and do
% a mass edit (the pencil icon in the top right of the bug tracker
% list) and move all bugs to the new milestone.
%
%\item Do the corresponding action in other ticket categories that
% have distinct release milestones.
% We are no longer doing this. Some of these sites are gone anyway.
%
%\item Create news items at \href{Linuxgames.com}{Linuxgames.com},
% \href{linux-gamers.com}{linux-gamers.com} and