somehow prepare the next dot release

Not sure of whether it should be in the ChangeLog or somewhere else in
the doc. Probably both, but I don't feel like refreshing the FAQ
tonight.

diff --git a/CMakeLists.txt b/CMakeLists.txt
index f12df62..3ef54ab 100644 (file)
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -106,8 +106,8 @@ endif()
 
 set(SIMGRID_VERSION_MAJOR "3")
 set(SIMGRID_VERSION_MINOR "19")
-set(SIMGRID_VERSION_PATCH "90")
-set(SIMGRID_VERSION_EXTRA "-DEVEL") # Extra words to add to version string (e.g. -rc1)
+set(SIMGRID_VERSION_PATCH "1")
+#set(SIMGRID_VERSION_EXTRA "-DEVEL") # Extra words to add to version string (e.g. -rc1)
 
 set(SIMGRID_VERSION_DATE  "2018") # Year for copyright information
 

diff --git a/ChangeLog b/ChangeLog
index ecc9454..288dd82 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,4 +1,42 @@
-SimGrid (3.20) NOT RELEASED YET (Release target: June 21. 2018 10:07 UTC)
+SimGrid (3.19.1) NOT RELEASED YET
+
+ The Fixed ABI Release.
+
+ As you may know, we are currently refactoring SimGrid in deep.
+ Upcoming SimGrid4 will be really different from SimGrid3: modular,
+ standard and extensible vs. layered, homegrown and rigid. C++ vs. C.
+
+ Our goal is to smooth this transition, with backward compatibility
+ and automatic update paths, while still progressing toward SimGrid4.
+
+ SimGrid remains open during works: The last pure SimGrid3 release was
+ v3.12 while all subsequent versions are usable alpha versions of
+ SimGrid4: Existing interfaces remain unchanged, but the new S4U
+ interface is budding and the internals are deeply reorganized.
+
+ Since 2015, we work hard to reduce the changes to public APIs. When
+ we need to rename a public library symbol in S4U, we let your
+ compiler issue an explicative warning when you use the deprecated
+ function. These messages remain for four releases, i.e. for one full
+ year, before turning into an error. Starting with v3.15, your can
+ also adapt to API changes with the SIMGRID_VERSION macro, that is
+ defined to 31500 for v3.15, to 31901 for v3.19.1 and so on.
+
+ Starting with this v3.19.1, our commitment to reduce the changes to
+ the public interfaces is extended from the API to the ABI: a program
+ using only MSG or SimDag and compiled against a given version of
+ simgrid can probably be used with a later version of SimGrid without
+ recompilation. We will do our best... but don't expect too much of
+ it, that's a really difficult goal during such profund refactoring.
+
+ The difference between v3.19 and v3.19.1 is that the former was
+ accidentally breaking the ABI of MSG, while the later is restoring
+ the previous ABI.
+
+ S4U and kernel APIs will still evolve until SimGrid4, with one-year
+ deprecation warnings as currently. In fact, cleaning up these
+ interfaces and converting them to snake_case() is one release goal of
+ v3.20. But don't worry, we are working to smooth this upgrade path.
 
 ----------------------------------------------------------------------------
 

diff --git a/NEWS b/NEWS
index 70334ce..9c13611 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -1,10 +1,13 @@
-                    _               _____  ____   ___
-__   _____ _ __ ___(_) ___  _ __   |___ / |___ \ / _ \
-\ \ / / _ \ '__/ __| |/ _ \| '_ \    |_ \   __) | | | |
- \ V /  __/ |  \__ \ | (_) | | | |  ___) | / __/| |_| |
-  \_/ \___|_|  |___/_|\___/|_| |_| |____(_)_____|\___/
-               (NOT RELEASED)
+                    _               _____  _  ___   _
+__   _____ _ __ ___(_) ___  _ __   |___ / / |/ _ \ / |
+\ \ / / _ \ '__/ __| |/ _ \| '_ \    |_ \ | | (_) || |
+ \ V /  __/ |  \__ \ | (_) | | | |  ___) || |\__, || |
+  \_/ \___|_|  |___/_|\___/|_| |_| |____(_)_|  /_(_)_|
 
+The Fixed ABI release.
+
+ * Reduce the changes to the binary interface of MSG
+   accidentally introduced by v3.19.
                     _               _____  _  ___
 __   _____ _ __ ___(_) ___  _ __   |___ / / |/ _ \
 \ \ / / _ \ '__/ __| |/ _ \| '_ \    |_ \ | | (_) |