Dear fellow developers, Please also beware of the following:
If you want to have a PR also in the release, then please mark it with milestone "Release 2019.10". Otherwise it will be missing from the release as I might not find the time to investigate and mark them myself or simply have no idea that they are suitable for the release. Once the marked PRs are merged into master, I will try to backport them to the release, make a new PR for the release (seems to be more work with github then with gitlab, sigh), and mark the original with label backported once it is merged. This also means that all PRs including fixes to the release need to made for master! Cheers, Markus On Mon, Oct 14, 2019 at 09:28:04AM +0200, Markus Blatt wrote: > Hi, > > as some might have noticed, I have created release branches (release/2019.10) > in the night from friday to saturday. > > Please be aware that up until now these are untested apart from our > usual jenkins tests run before their creation. You are of course welcome to > test them yourself, but if you want to prevent double work you should wait > until I did run some tests and verified that they work as expected. > > If somebody already verified this, please yell. > > Cheers, > > Markus > > -- > Dr. Markus Blatt - HPC-Simulation-Software & Services http://www.dr-blatt.de > Pedettistr. 38, 85072 Eichstätt, Germany, USt-Id: DE279960836 > Tel.: +49 (0) 160 97590858 > _______________________________________________ > Opm mailing list > Opm@opm-project.org > https://opm-project.org/cgi-bin/mailman/listinfo/opm -- Dr. Markus Blatt - HPC-Simulation-Software & Services http://www.dr-blatt.de Pedettistr. 38, 85072 Eichstätt, Germany, USt-Id: DE279960836 Tel.: +49 (0) 160 97590858 _______________________________________________ Opm mailing list Opm@opm-project.org https://opm-project.org/cgi-bin/mailman/listinfo/opm
