X-Git-Url: http://info.iut-bm.univ-fcomte.fr/pub/gitweb/simgrid.git/blobdiff_plain/c04075c49b6bc68df4f37240b4ac53e7a108abaa..dbd3324fa25de8398de0490788ba670d9df4be1d:/ChangeLog

diff --git a/ChangeLog b/ChangeLog
index e4e795874f..1419d43701 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -3,35 +3,43 @@
 SimGrid (3.29.1) NOT RELEASED YET (v3.30 expected December 21. 2021, 15:59 UTC)
 
 Main user-visible changes:
- - The SimDag API for the simulation of the scheduling of Directed Acyclic 
-    Graphs has been dropped. It was marked as deprecated for a couple of years. 
-    We finally complete the implementation of what has been called SimDag++ 
-    internally, i.e., porting the different features of SimDag on top of S4U. 
-    The new way to simulate the execution of dependent activities directly by 
-    maestro (without any other actor) is details in the examples/cpp/dag-* series
-    of examples. 
- - The removal of SimDag led us to also remove the export to Jedule files that 
-   was tightly coupled to SimDag. The instrumentation of DAG simulation is still 
-   possible through the regular instrumentation API based on the Paje format. 
-   
+ - The SimDag API for the simulation of the scheduling of Directed Acyclic
+   Graphs has been dropped. It was marked as deprecated for a couple of years.
+   We finally complete the implementation of what has been called SimDag++
+   internally, i.e., porting the different features of SimDag on top of S4U.
+   The new way to simulate the execution of dependent activities directly by
+   maestro (without any other actor) is details in the examples/cpp/dag-* series
+   of examples.
+ - The removal of SimDag led us to also remove the export to Jedule files that
+   was tightly coupled to SimDag. The instrumentation of DAG simulation is still
+   possible through the regular instrumentation API based on the Paje format.
+ - We also dropped the old and clumsy Lua bindings to create platforms in a
+   programmatic way. It can be done in C++ in a much cleaner way now, which
+   motivates this suppression.
+
 S4U:
+ - Introduce on_X_cb() functions for all signals, to attach a new
+   callback to the signal X. The signal variables are now hidden and
+   only these functions should be used.
+   Rationale: this enables the usual deprecation schema where functions
+   remain for 4 releases if we need to modify the signals, while the
+   current code with the signal variables directly visible prevents any
+   smooth transition.
  - New function: Engine::run_until(date), to split the simulation.
  - New signal: Activity::on_veto, to detect when an activity fails to start.
  - New function: Engine::track_vetoed_activities() to interrupt run()
    when an activity fails to start, and to keep track of such activities.
    Please see the corresponding example for more info.
- - Introduce on_X_cb() functions for all signals, to attach a new
-   callback to the signal X. The signal variables are now hidden and
-   only these functions should be used.
-   Rational: this enables the usual deprecation schema where functions
-   remain for 4 releases when we need to modify the signals, while the
-   current code with the signal variables directly visible prevent any
-   smooth transition.
 
 SMPI:
  - Dynamic costs for MPI operations: New API to allow users to dynamically
- change injected costs for MPI_Recv, MPI_Send and MPI_Isend operations.
- Alternative for smpi/or, smpi/os and smpi/ois configuration options.
+   change injected costs for MPI_Recv, MPI_Send and MPI_Isend operations.
+   Alternative for smpi/or, smpi/os and smpi/ois configuration options.
+
+XBT:
+ - Function xbt::Extendable::get_data() is now templated with the type of the
+   pointee. Untyped function is deprecated. Use get_data<void>() if you still
+   want to retrieve void*.
 
 Documentation:
  - New section: "SimGrid MPI calibration of a Grid5000 cluster"
@@ -44,6 +52,8 @@ Python:
 
 Fixed bugs (FG#.. -> FramaGit bugs; FG!.. -> FG merge requests)
  (FG: issues on Framagit; GF: issues on GForge; GH: issues on GitHub)
+ - FG#95: Wrong computation time for multicore execution after pstate change
+ - FG#97: Wrong computation time for ptask+multicore+pstates
  - FG#99: Weird segfault when not sealing an host
 
 ----------------------------------------------------------------------------