New MAJOR release 02.00.00

Changes since 01.06.01:

- Update for the latest DeviceAccess 02.00 API
- Allow to obtain TypeChangingDecorators with different types for the same target
- If receiver does not have wait_for_new_data, write returns always false (= no data lost)
- Proper implementation of synchronous process arrays (without wait_for_new_data)
- Block creation of BiDirectionalProcessArray without wait_for_new_data
- ReferenceTestApplication: allow to detect queue overflows

- Remove deprecated SynchronizationUtilities and ProcessVariableListeners
- Change SynchronizationDirection enum into strongly-typed one.

- Fix issues reported by clang address/thread sanitizers

Tag for the group focus in 2020 calendar week 17

Tag to create a consistent set of DeviceAccess, ControlSystemAdapter and ApplicationCore which compile and all DeviceAccess and ApplicationCore tests are passing (except for race conditions)

New PATCH release 01.06.01

Changes since 01.06.00:
- make sure initial values are always sent exactly once when using the PersistentDataStorage
- Fix incorrect pre/post read/write logic.

New MINOR release 01.06.00

Changes since 01.05.02:

- Fix persist data storage blocking the csa (#21)
- Set data validity to faulty on receiving end by default (starting value) -> slight behaviour change!
- Use new null VersionNumber to mark the invalid version number at construction time

New PATCH release 01.05.02

Changes since 01.05.01:

- fixes in the build system
  -- solves issues mainily with newer Boost versions (>=1.71)

New PATCH release 01.05.01

Changes since 01.05.00:

- Made persistency layer work with bidirectional variables and added tests for it. Solves #20

New MINOR release 01.05.00

Changes since 01.04.00:

- Fixed potential data races in PersistentDataStorage
- Tests: Add dataValidity flag to ReferenceTestApplication

New MINOR release 01.04.00

Changes since 01.03.00:

- Introduce DataValidity flag for ProcessArray
- Changes to build environment
- BidirectionalProcessArray is now no longer experimental
- Allow writeDestructively() always, as this is now part of the DeviceAccess interface. This change is technically an interface change, but only ApplicationCore should be affected right now.

New MINOR release 01.03.00

Changes since 01.02.00:

- improved ReferenceTestApplication: allow setting the version used in write operations

New MINOR release 01.02.00

Changes since 01.01.00:
- Added int64_t, uint64_t and std::string to all tests where the supported data types are checked
- Extended the ReferenceTestApplication with PV for int64_t, uint64_t and std::string
- TypeChangingDecorator now works for std::string as user type
- Reactivated tests for persistent data storage (they seem to be stable now)

New MINOR release 01.01.00

Changes since 01.00.00:
- Added int64/uint64 to the ReferenceTestApplication
- Fixed compilation on non-linux platforms
- Added an (optional) value reject callback, which is used by ApplicationCore testable mode to keep track of the number of values
- Fixed implementation of bi-directional variables, incl. tests that would catch wrong implementations
- Fixed incompatibility with boost 1.68 - boost::fusion::for_each() passes now the callable object by value, not by reference.

New MAJOR release 01.00.00

Changes since 00.14.00:

necessary change for recent DeviceAccess update:
- TimeStamp has been integrated into the VersionNumber. TimeStampSource etc. has therefore been removed and the interface is changed accordingly.
- The new exception scheme is now consistently used

New MINOR release 00.14.00

Changes since 00.13.00:

- necessary update for new release of DeviceAccess (new readAsync implementation)
- allow specifying the AccessModeFlags like wait_for_new_data

- added performance test (executed in ctest but not comparing the performance automatically)
- converted test into AUTO_TEST_CASEs

- removed c++11 flag as it interferes with the c++14 flag coming from DeviceAccess
- use correct linker flags on macOS.

New MINOR release 00.13.00

Changes since 00.12.00:

- fixed some bugs in the PersistentDataStorage which could lead to unneeded entries in the .persist files after changing the variable household

New PATCH release 00.12.01

Changes since 00.12.00:

- fixed some bugs in the PersistentDataStorage which could lead to unneeded entries in the .persist files after changing the variable household

New MINOR release 00.12.00

Changes since 00.11.01:

- Fixed the rare bug running into the assert(queueHasData || tripleBufferHasData) in doPostRead when using readLatest() and added tests for this.
- added an option to enable a thread safety check, which raises an assert when a ProcessArray object is used from different threads
- Minor code cleaning

New PATCH release 00.11.01

Changes since 00.11.00:

- Fixed (usually uncaught) exceptions when reading the persistency file if the variable household changed. Added tests for different scenarios.

New MINOR release 00.11.00

Changes since 00.10.00:

- required changes for the latest DeviceAccess update

- fixed mayReplaceOther() of the TypeChangingDecorator, which was leading to wrong behaviour inside a TransferGroup
- expect a const reference in getDecorator() instead of a non-const reference, to allow passing rhs references

New MINOR release 00.10.00

Changes since 00.09.00:

- Required changes for latest DeviceAccess
- Added experimental support for bidirectional variables

New MINOR release 00.09.00

Changes since 00.08.00:

- fix crash when using createProcessArray() with std::string data type

- Prevent decorating the same ProcessArray with the TypeChangingDecorator multiple times (instead reuse the same decorator)

- improved documentation