info_etc how file: fewer dependencies (more custom/specialised build specs) when building custom environment (gcc et. al.) on the FreeBSD box.
More aggressive hardcoded defaults for the server.h in converger (visited_places et. al. to deal with hashtables and so on). Should be inline with the anticipation of a more capable hardware being introduced in the near future. Todo -- later on must provide a runtime parametric configuration mechanism (e.g. a CLI arg).
A Big Commit (ABC) -- C++ related coding changes; introduction of a new computational model (multilogit -- a latent-class-like model);  GUI interface changes, etc.

Expect bugs (inclusive of regression ones). Changes are, somewhat, outlined as follows:

*) Bug fix -- control value (chosen attribute code) did not work correctly if negative values were present! Affected models -- gmnl2a, mixed_logit, gmnl2.

*) Bug fix -- do_redistribute_remaining_complexities could have a case where accumulated_duplicates was empty yet was being subtracted from the map.

*) Continuous variables/attributes (with subsequent refactoring of the matrix_composite format -- now 'y' vector is a separate object/array and the matrix_composite is made up from floats).

*) Alphanumeric values for respondent, alternative and choice-set columns in datasets.

*) Minor speed improvement when non-first attribute's code/value is zero (now explicitly skipped).

*) Allowing for respondents, alternative and choice_set to be strings (as opposed to integer only requiremnt in the previous versions).

*) Slightly faster csv.column< ::std::string> implementation.

*) Introducing coroutines for the pseudo-cooperative interruptability of the server when processing large visited_places/remaining_complexities. An alternative of breaking-up the on_sync_timeout method into multiple async sub-methods is plausible, and in fact likely for the future versions (where visited_places processing can be done in a parallel-spread with various assistive processes), but currently the coroutine is used as an intermediate solution because it offers the least-intrusive mechanism w.r.t. current, non-interruptable, codebase. If, later on, one needs to take-out the coroutine mechanisms -- just search for 'courotine' and take out the related code.

*) A new computational model -- multi logit (i.e. latent classes). Still very much in experimental (highly likely very buggy) stage.

*) Reworking the structure of thrown/caught exceptions (more descriptive, as well as generalised, types are now present -- catering for greater flexibility in user code determining what and when to catch/rethrow/ignore). Still more to be done/refactored in plenty of places in the existing code-tree, but it's a start.

*) Making parsing mechanisms more robust during controller's addition of a new task -- currently by way of catching more exceptions (e.g. lexical cast, etc.) -- with occasional re-throwing at the dataset_1 controller level (to be done more of the same later on).

*) Cleaner API calls (and taking out redundant includes) w.r.t. controller architecture.

*) Some server architecture also has more restricted message typedefs being passed around between different modules.

*) Visited places numeric representation change:

**) GMP -- gnu mp repacement of libBN for absolute-coordinates of visited places (for performance related reasons/experiments).

**) moving bin_int et. al. to use ::std::shared_ptr from ::boost::shared_ptr

*) GUI changes:

**) minor visual re-styling.

**) minor verbal correction/spelling.

**) adjusted max-complexity's default value et. al. -- this is especially relevant in light of new, potentially more memory-hungry -exhaustive, models being introduced (e.g. multi logit).

**) centering of some text in "adding of a new task" window.

**) 'range' row of coefficients in tasks' list has a lighter shade of yellow.

**) button margins throughout the web interface have been increased somewhat.

**) in the context menu (when adding a new task) -- hiding specific context buttons when such are not applicable (e.g. to/from range does not have 'fill to bottom and right' option and so it's button is hidden altogether).

**) ios and android devices now exclude the button:hover CSS styling (otherwise a 'stuck' button-effect was experienced... after the button was tapped and done-with, the style still showed it as being active/highlighted/hovered-over).

**) index.html -- deleted redundant variable in 'calculate_normalised_betas' function.

*) Building/compiling gcc/boost/et.al. info update (inclusive of building GMP and single-threaded asio in latest version of boost 1.54).

*) Migrated the codebase to use current (non-deprecated) calls to libarchive.