Changes between Version 296 and Version 297 of LnDevel

Timestamp:

May 29, 2025, 5:43:46 PM (3 days ago)

Author:

lnerger

Comment:

--

LnDevel

@@ -168 +168 @@
 1. We have marked this release as a beta-release mainly because of the large changes in the code. While we have tested this release carefully with different applications, we cannot exclude that there are issues that we didn't find. We like to motivate all users to test PDAF V3.0 and to let us know possible issues (using the Issues-function in Github or by email to pdaf\@awi.de). This will help us to fix such issues so that the final release for PDAF V3.0 can hopefully be released in 2-3 months. During this time, we will also finalize the documentation to reflect all changes.
 
-2. PDAF V3.0 is not fully backward compatible, due to the modernization of the code. Thus, with this release, it is not possible to just compile and link with existing implementations like in previous releases. The required adaptions are, however, small. (Please see https://pdaf.awi.de/trac/wiki/PortingToPDAF3 for a description of how to adapt your existing code for PDAF V3.0). Below the code changes affecting backward-compatibility are also described.
-
-3. Information for porting and about new features can be found at:
-* https://pdaf.awi.de/trac/wiki/PortingToPDAF3
-* https://pdaf.awi.de/trac/wiki/PDAF3_new_functionality
+2. PDAF V3.0 is not fully backward compatible, due to the modernization of the code. Thus, with this release, it is not possible to just compile and link with existing implementations like in previous releases. The required adaptions are, however, small. Below the code changes affecting backward-compatibility are also described.
+
+3. Information for using PDAF3 and about new features can be found at:
+* Porting to PDAF3: https://pdaf.awi.de/trac/wiki/PortingToPDAF3
+* New features: https://pdaf.awi.de/trac/wiki/PDAF3_new_functionality
 
 Major changes with effect on backward-compatibility