+SimGrid (3.7.1) stable; urgency=low
+
+ MSG:
+ * Restore the prototype of MSG_process_create_with_environment() to
+ the pre-3.7 situation by removing the kill_time argument.
+ * Add a MSG_process_set_kill_time() function instead.
+
+ SURF:
+ * Fix weird behaviors when dealing with parallel tasks.
+
+ WINDOWS:
+ * Simgrid is now built as a dll.
+ * Simgrid-java now works on Windows.
+ * Simgrid-Java is now included into Windows package.
+
+ MacOS:
+ * First pre-build package for MacOSX.
+
+ Build System:
+ * Fix compilation when using MSG_USE_DEPRECATED.
+ * Fix some compilation issues on Macs and Windows.
+ * Reduce the number of failing tests on exotic systems, like Debian/Hurd.
+ * Environment variables CFLAGS and LDFLAGS are now honored by cmake.
+
+ We discovered that the Lua console is broken, but we are missing the
+ manpower to fix it right now. The problem existed in 3.7 too, so we
+ are not blocking the release for that. Sorry if you depended on this
+ feature, any help would be really welcome.
+
+ -- Thu Jun 7 2012 Da SimGrid team <simgrid-devel@lists.gforge.inria.fr>
+
SimGrid (3.7) stable; urgency=low
The "spring cleanups (before the next Big Project kicks in)" release.
- contexts/synchro: Synchronization mode to use when running
contexts in parallel (either futex, posix or busy_wait)
- contexts/parallel_threshold: Minimal number of user contexts
- that must be part of a scheduling round to switch to parallel
+ that must be part of a scheduling round to switch to parallel
execution mode (raw contexts only)
+ * Fix bugs that prevented to use suspend/resume along with
+ synchronization structures.
+ * Fix bugs in process termination that lead to invalid memory access
+ in very specific conditions.
SURF:
* Introduce a parallel mode for the models (controlled by surf/nthreads
-- Wed Oct 5 15:51:01 CEST 2011 Da SimGrid team <simgrid-devel@lists.gforge.inria.fr>
-
SimGrid (3.6.1) stable; urgency=low
The "Oops, we broke Macs too" release
[contributed by Sékou Diakite, many thanks]
GRAS:
- * Introduce a listener thread in charge of receiving incomming
+ * Introduce a listener thread in charge of receiving incoming
messages from the network. It allows to overlap communication and
computation but most notably, it removes some stupid deadlocks due
to the fact that so far, a process could not send and receive at
