Dear OPM community! We are now in September, and since we have planned to do a 2013.09 release, we should agree on how to do it. The following are some suggestions.
1. Each maintainer (as given on http://www.opm-project.org/wiki/index.php/Main_Page near the bottom) is responsible for branching and tagging in his own repo. 2. The opm-verteq and opm-autodiff modules are new and will get a presence on the opm web page, docs etc. I would add opm-benchmarks too, but who is maintainer for opm-benchmarks? 3. Last time we made a release branch early, and most work with the release took place there. This may not be the best way to do things this time around, feel free to make suggestions. In any case we should use the same naming approach as last time. The branch name used should be release/2013.09, and tag names should be release/2013.09/rc1 etc. counting up, with release/2013.09/final equal to the last rc tag. 4. For the new modules, some refactoring and documentation work is anticipated. For the existing modules, I do not expect much, other than what has been done in the course of regular development since last release. There is one exception, I think we should move away from nested namespaces. They are used only in a few places, and inconsistently at that. Using a directory == namespace approach is not very well suited, since it will nest our namespaces far deeper than practical, so I think the best is to keep everything in namespace Opm. Please make noise if you disagree! There are some cases I could consider to be exempt, such as in Units.hpp. 5. I suggest Thursday September 19 for release day. In order to have packages built, the last changes should be in Monday September 16. Arne Morten is going to build packages, and I hope 3 days are sufficient. Atgeirr Flø Rasmussen _______________________________________________ Opm mailing list [email protected] http://www.opm-project.org/mailman/listinfo/opm
