Dear DuMux community,

The time has come to collect our work for the next Dumux release: Dumux
3.9!

Regarding this exciting news, I would like to announce some scheduling
aspects and other important information.

Please consider the following dates while developing new features and
adding merge requests to Dumux:

== Soft Feature Freeze: 7. June, 2024 (3 weeks prior to the release) ==
- All major changes that should be included and are not yet committed
should be announced. Add a comment to
Issue#1364<https://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/issues/1364
> describing the feature and the areas affected by the change.
- Major changes not announced before the soft freeze will be reserved
for the next release.
- The representative assigned to each major task will report on their
remaining tasks.

== Hard Feature Freeze: 14. June 2024 (2 weeks prior to the release) ==
- All major changes must be committed before the hard feature freeze.
- Large invasive fixes are only accepted after consultation with the
release manager (small fixes are ok).
- Try to get your bugs fixed, your tests included, and your
documentation written before the hard feature freeze.
- The representative assigned to each major task will give a final
report on what was finished and what must be postponed until the next
release.

== Final Testing:  21. June 2024 (1 week prior to the release) ==
- No further commits are allowed, barring those performed by the
release manager, or under the explicit authorization of the release
manager.
- Release candidate packages will be provided.
- Tests will be performed on various systems, compilers, and under
different conditions. Everyone should at least test their own tests!

== DuMuX 3.9 Release: 28. June 2024 ==
- Cold beverages, great discussions, and even better research code.


Looking forward to a fantastic release,

Leon
(Release manager DuMux 3.9)
_______________________________________________
DuMux mailing list
[email protected]
https://listserv.uni-stuttgart.de/mailman/listinfo/dumux

Reply via email to