Skip to content
Snippets Groups Projects
Commit 1e4612c5 authored by Andre Maroneze's avatar Andre Maroneze
Browse files

[dev] extend set-version.sh and update release manual

parent 21641125
No related branches found
No related tags found
No related merge requests found
......@@ -88,7 +88,7 @@ else
echo "$NEXT_CODENAME" >VERSION_CODENAME
# Opam files
$SED -i "s/^version: .*/version: \"$NEXT_MAJOR.$NEXT_MINOR\"/g" opam
$SED -i "s/^version: .*/version: \"$NEXT\"/g" opam
$SED -i "s/\(.*\)$CURRENT_MAJOR.$CURRENT_MINOR-$CURRENT_CODENAME\(.*\)/\1$NEXT_MAJOR.$NEXT_MINOR-$NEXT_CODENAME\2/g" opam
$SED -i "s/^version: .*/version: \"$NEXT_MAJOR.$NEXT_MINOR\"/g" tools/lint/frama-c-lint.opam
......@@ -113,7 +113,7 @@ else
$SED -i "s/\($WP_CL_MSG_FUTURE\)/\1\n$FC_CL_LIN\n\n$FC_CL_LIN\n$WP_CL_MSG_NEXT/g" src/plugins/wp/Changelog
# API doc
find src -name '*.ml*' -exec $SED -i -e "s/Frama-C+dev/${NEXT}-${NEXT_CODENAME}/gI" '{}' ';'
find src -name '*.ml*' -exec $SED -i -e "s/Frama-C+dev/${NEXT_MAJOR}.${NEXT_MINOR}-${NEXT_CODENAME}/gI" '{}' ';'
# Manuals changes
$SED -i "s/\(^\\\\section\*{Frama-C+dev}\)/%\1\n\n\\\\section\*{$NEXT_MAJOR.$NEXT_MINOR ($NEXT_CODENAME)}/g" \
......@@ -126,6 +126,10 @@ else
src/plugins/e-acsl/doc/userman/changes.tex
# Frama-C build script
$SED -i "s/(\\\\\\\"frama-c\\\\\\\" (>= [1-9][0-9]\.[0-9]))/(\\\\\\\"frama-c\\\\\\\" (>= $NEXT_MAJOR.$NEXT_MINOR))/g" bin/frama-c-build-scripts.sh
# Reference configuration
$SED -i "s/Frama-C [1-9][0-9]\.[0-9]/Frama-C $NEXT_MAJOR.$NEXT_MINOR/gI" \
reference-configuration.md
fi
......@@ -3,6 +3,13 @@
That is the procedure for forking the release from \texttt{master}.
\section{Creating the milestones}
Create the milestone for the next releases on \textsf{Gitlab},
in the Frama-C group. They will be used for development that will not
be integrated into the upcoming release.
\expertise{François, Julien}.
\section{``Freezing'' master}
When the ``freeze'' period arrives (usually a few weeks before the beta
......@@ -48,15 +55,11 @@ and go through Merge-requests. Everything else should go in \texttt{master},
which can then be reset to standard-level protection (Developers + Maintainers
allowed to push/merge).
\section{Creating the milestones}
Create the milestone for the next release on \textsf{Gitlab},
in the Frama-C group
\expertise{François, Julien}.
\section{GitLab issues}
{\em This is currently done periodically in specific Frama-C meetings, so only
a final check is usually necessary.}~\\
Check public issue tracker at \url{https://git.frama-c.com/pub/frama-c/issues/}.
All issues should have been at least acknowledged: at least they should be
assigned to someone, preferably tagged appropriately.
......@@ -80,6 +83,7 @@ This will:
\item update the \texttt{opam} files (Frama-C, lint, hdrck)
\item update the API doc
\item update the Frama-C build script
\item update the reference configuration
\end{itemize}
Merge the \texttt{stable} branch in the \texttt{master} branch.
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment