Skip to content
Snippets Groups Projects
Commit 23fe948f authored by Timo Koch's avatar Timo Koch
Browse files

[changelog] Add boundary types and comment about previously deprecated now deleted code

parent b1f04df8
No related branches found
No related tags found
1 merge request!2183[changelog] Add boundary types and comment about previously deprecated now deleted code
...@@ -7,10 +7,16 @@ Differences Between DuMu<sup>x</sup> 3.3 and DuMu<sup>x</sup> 3.2 ...@@ -7,10 +7,16 @@ Differences Between DuMu<sup>x</sup> 3.3 and DuMu<sup>x</sup> 3.2
### Immediate interface changes not allowing/requiring a deprecation period: ### Immediate interface changes not allowing/requiring a deprecation period:
- For the "sequential" models, the property `BoundaryTypes` has been simply renamed to `SequentialBoundaryTypes`
### Deprecated properties/classes/functions/files, to be removed after 3.3: ### Deprecated properties/classes/functions/files, to be removed after 3.3:
- The property `BoundaryTypes` has been deprecated. The boundary condition type can now be deduced from the problem type using `ProblemTraits`.
### Deleted classes/files, property names, constants/enums: ### Deleted classes/files, property names, constants/enums:
- Everything that has been deprecated before release 3.2 has been removed.
### Other noteworthy changes: ### Other noteworthy changes:
- after release 3.2, DuMu<sup>x</sup> releases earlier than 2.12 will no longer be automatically tested or supported. - after release 3.2, DuMu<sup>x</sup> releases earlier than 2.12 will no longer be automatically tested or supported.
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment