Update CHANGELOG.md for CodeRT 2.0.2 release

Author: chaitanyavalli-r

docs-sources/releases/CHANGELOG.md

@@ -1,3 +1,17 @@
+# 2.0.2 (2024-12-12 08:09)
+1. The C++ 23 language standard is now supported. However, C++ 17 is still the default language standard for the code generator.
+2. Built-in [build tasks]({$vars.doc.server$}/building/build-tasks/) are now available for building any TC that is present in the workspace. These build tasks will build TCs using the Art Compiler in the integrated terminal. A convenient way to run these build tasks is through the **Terminal - Run Build Task** command.
+3. The Art Debugger can now show the active state of a capsule instance in the Art Debug view. A new button in the toolbar has been added which controls if the name of the active state should be shown (and if so, if the simple or qualified state name should be used).
+4. The Art Debugger now by default builds a TC before it is launched. It's built in the same way as if you would have performed the **Build** command on the TC. This behavior can be disabled by setting a new launch configuration attribute `buildBeforeLaunch` to `false`. You may want to do this if you have set the `preLaunchTask` attribute to specify a build task that builds the application in some other way.
+5. The Art Debugger provides a new command **Send to App** which can be used during a debug session. It allows to pass a custom command to the debugged application which can be handled in the TargetRTS function `RTToolsetObserver::handleSendToApp()`. It can for example be used for implementing custom trace commands that can help when debugging. See [the documentation]({$vars.doc.server$}/running-and-debugging/debugging/#custom-debug-commands) for more information.
+6. Content assist for type descriptor definitions has been improved to include a comment with a link to the documentation which describes how to implement a type descriptor.
+7. A new command **Open Log File** is now available. It will open the log file that is used by Code RealTime for logging internal errors and other diagnostic messages that can be useful when troubleshooting and when reporting an issue.
+8. The C++ code generator and TargetRTS now supports the primitive type `long double`.
+9. The C++ code generator now supports use of shallow history in class state machines.
+10. A new sample [MatMult]({$vars.github.repo$}/tree/main/art-samples/MatMult) is provided. It implements multiplication of matrices and shows how unwired ports and message deferral (among other things) can be used.
+11. The support for Art files in Model RealTime has improved and is no longer experimental. It's now possible to inherit from Art protocols, send Art events with parameters of any type, and use an Art capsule as the type of a capsule part in the model. Furthermore the Art compiler is now automatically invoked when building a prerequisite Art TC through the Model Compiler. See the [Model RealTime documentation](http://model-realtime.hcldoc.com/help/topic/com.ibm.xtools.rsarte.webdoc/Articles/Integrations/Code%20RealTime%20Integration.html) for more information about how to use Code RealTime and Model RealTime together and which limitations that still apply.
+12. A first version of an Art Exporter utility for Model RealTime is available. It exports (parts of) a Model RealTime model into Art files and is useful if you want to migrate (fully or partially) an application from Model RealTime to Code RealTime. This first version currently only supports exporting type definitions (enums, classes, type aliases etc) to corresponding C++ types defined in Art files.
+
 # 2.0.1 (2024-11-11 07:03)
 1. The C++ code generator now supports trigger guards, both for capsule and class state machines. For a capsule example, see [this sample]({$vars.github.repo$}/tree/main/art-comp-test/tests/capsule_trigger_guard). For a class example, see [this sample]({$vars.github.repo$}/tree/main/art-comp-test/tests/class_trigger_guard).
 2. Now you can use the `rule_config` property on capsule parts, which means it's now possible to disable validation rules for individual parts. This is for example useful for disabling [ART_0039_portPartMultiplicityMismatch]({$vars.doc.server$}/validation/#art_0039_portpartmultiplicitymismatch) for ports that are intentionally left unconnected (for example because you plan to send events on them using the Art Debugger). In addition the `rule_config` property is now also supported on entry and exit points.