Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
F
frama-c
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Container Registry
Model registry
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
pub
frama-c
Commits
30132b18
Commit
30132b18
authored
4 months ago
by
Virgile Prevosto
Browse files
Options
Downloads
Patches
Plain Diff
[release] Indicate that the versions of ACSL and E-ACSL should stay synchronized
parent
cc31f02b
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/release/validation.tex
+5
-1
5 additions, 1 deletion
doc/release/validation.tex
with
5 additions
and
1 deletion
doc/release/validation.tex
+
5
−
1
View file @
30132b18
...
@@ -80,7 +80,11 @@ by issuing \texttt{make check-devguide}\todo{Fix this}.
...
@@ -80,7 +80,11 @@ by issuing \texttt{make check-devguide}\todo{Fix this}.
\subsection
{
Manuals
}
\subsection
{
Manuals
}
Manuals are built by the continuous integration. However, the Release Manager
Manuals are built by the continuous integration. However, the Release Manager
should check whether a new version of ACSL or E-ACSL must be released.
should check whether a new version of ACSL or E-ACSL must be released. Note that
an ACSL release must be accompanied by an E-ACSL (the language, not the plug-in)
release, at least to acknowledge the fact that the changes in ACSL do not impact
E-ACSL. It might also be useful to check that the table of contents of both manuals
coincide
\todo
{
Provide a script for that
}
.
Also, most of the manuals include an appendix with the list of changes that have
Also, most of the manuals include an appendix with the list of changes that have
happened, divided by version of Frama-C. Make sure that the first section has
happened, divided by version of Frama-C. Make sure that the first section has
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment