-SimGrid (3.1.1) unstable; urgency=low
-
- * Documentation update:
- - New FAQ: "Valgrind spits tons of errors!"
- - GRAS tutorial containing an introduction both to the GRAS framework
- and to the used communication model as well as an initiatic tour
- introducing the most proheminent features. Current tour TOC:
- # Lesson 0: Installing GRAS
- # Lesson 1: Setting up your own project
- # Lesson 2: Exchanging simple messages
- # Lesson 3: Passing arguments to the processes (in SG)
- # Lesson 4: Attaching callbacks to messages
- # Lesson 5: Using globals in processes
- # Lesson 6: Logging informations properly
- # Lesson 7: Using internal timers
- # Lesson 8: Handling errors through exceptions
- More a due, of course. At least the one explaining how to add data
- into messages. In the meanwhile, you can check the examples which are
- still here.
-
+SimGrid (3.3-cvs) unstable; urgency=low
+
+ OVERALL CHANGES:
+ * Make the backtrace of exceptions more human readable [Mt]
+
+ --
+
+SimGrid (3.2) unstable; urgency=low
+
+ OVERALL CHANGES:
+ * Port to windows.
+ We still experience issues on this platform, but we belive that at
+ least MSG is usable.
+
+ GRAS API BREAKAGE (for simplification purpose, sorry):
+ * the gras_msgtype_by_name is not used anymore. Instead of
+ gras_msg_send(toserver, gras_msgtype_by_name("request"), &request);
+ you can write (and must)
+ gras_msg_send(toserver, "request", &request);
+ - If you still want to pass a gras_msgtype_t to the function (to cache
+ the type and avoid the lookup time), use the gras_msg_send_() variant.
+ - Impacted functions:
+ gras_cb_register, gras_cb_unregister, gras_msg_send, gras_msg_wait,
+ gras_msg_rpccall, gras_msg_rpc_async_call, gras_msg_wait_ext
+ * The callbacks are now expected to return 0 when everything went well
+ (just like the main() function)
+
+ GRAS new features and improvements:
+ * New module mecanism where user code can use per process globals [Mt]
+ This is similar to gras_userdata_*() functions, but for libraries. It
+ factorize some code developped over and over in the examples and AMOK.
+ It has still to be documented and used (only amok/peermanagement is
+ converted for now).
+ * Fix a vicious bug in the TCP buffering mecanism which leaded to message
+ loss when they were small enough to fit into the buffer and sent quickly
+ enough so that they can all get received in one shoot.
+ * gras_datadesc_by_name and gras_msgtype_by_name: now raise an exception
+ if not found. Use the *_or_null() variant for the old semantic.
+ * In gras_msg_handle, do not discard messages without callback.
+ They are probably messages to be explicitly awaited later (ie, proofs of
+ mis-synchronization in userland since they are sent before being awaited)
+ No big deal usually.
+ * gras_socket_meas_send/recv: semantic changed!
+ The numerical arguments used to be (1) the total amount of data to send
+ and (2) msg_size. This was changed to (1) msg_size and (2) amount of
+ messages. This was need for the fool willing to send more than MAXINT
+ bytes on quite fat pipes.
+
+ AMOK:
+ * Do really rename the hostmanagement module to peermanagement. [Mt]
+ Ie, rename functions from amok_hm_* to amok_pm_*. This breaks the API,
+ but this is rather new and this was documented in the module
+ documentation (poor excuses, I admit)
+ * Bandwidth measurement semantic changed! This follows the changes to
+ gras_socket_meas_send/recv explained above.
+