Dear DuMuXers,
as the release manager, I would like to announce the schedule and
important information for the next DuMuX release, DuMuX 2.11.
Consider following dates in your development / commit strategy:
== Soft feature freeze: March 10==
- All major changes that should be included and are not yet committed
should be announced. Add a comment to issue #366
<https://git.iws.uni-stuttgart.de/dumux-repositories/dumux/issues/366>
describing the feature and areas affected by the change.
- Major changes not announced will be rejected after the soft freeze.
- Reports from the management representatives about remaining tasks.
== Hard feature freeze: March 17 ==
- All major changes must be committed before the hard feature freeze.
- Invasive fixes which might break other code 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.
- Final reports from the management representatives what is finished and
what must be dropped.
== Final testing: March 27 ==
- No commits are allowed except these which are done by the release
manager or which are explicitly authorization by the release manager.
- Release candidate packages will be provided.
- Tests on various systems, compilers, with different settings are run.
Everyone should at least test the own tests!
== DuMuX 2.11 release: March 31 ==
- celebrate DuMuX and Rainer's birthday.
All commits violating this plan will be reverted without further comment.
Looking forward to a good release,
Sina
(Release manager DuMuX 2.11)
_______________________________________________
Dumux mailing list
[email protected]
https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
