> Cut-off date for code changes: Tuesday April 11, 2017. The master branches of > all modules will be closed for non-trivial, non-regression and non- > documentation merges after this, i.e., I'll be a jerk and personally revert > any merged code changes that do not fix serious problems thereafter.
I don't know if I understand you correctly here, but I hope you can clarify. Why can't every module simply make a release 2017-04 that is frozen from April 11, and then you can simply pick that one, and we can go on doing development as usual in the master branch? It's simple to just update the release and cherry-pick from master if need be. This will also be a lot less invasive (and sane?). But I probably misunderstood something. - Pål ------------------------------------------------------------------- The information contained in this message may be CONFIDENTIAL and is intended for the addressee only. Any unauthorised use, dissemination of the information or copying of this message is prohibited. If you are not the addressee, please notify the sender immediately by return e-mail and delete this message. Thank you _______________________________________________ Opm mailing list [email protected] http://opm-project.org/cgi-bin/mailman/listinfo/opm
