On 14/10/13 17:19, Arne Morten Kvarving wrote:
On 11/10/13 18:28, Bård Skaflestad wrote:
All,
I have just created the release branch (release/2013.10) and tagged the
first release candidate (release/2013.10/rc1) in preparation of the
2013.10 OPM release in the following modules
* opm-core
* opm-autodiff
* dune-cornerpoint
* opm-porsol
* opm-upscaling
* opm-benchmarks
At this time, we are in bug fixing and regression testing mode only. We
don't expect to include any new features in the release.
I encourage testing (i.e., building and running) the software suite and
reporting any issues to the mailing list or in the GitHub issue tracker.
Sincerely,
packages are all queued up on launchpad.
things we can do better the next time (it's only meant constructive!);
1) don't call a release before all maintainers have signed off.
opm-verteq and opm-material was missing. for verteq, roland responded
quickly, so that's built. for opm-material, i got no response (i'm not
expecting anyone to sit around waiting for my emails, or anything..)
as this is smack in the middle of the dependency chain, i had no other
option but to push out current master to get my job done. i would
never do it for a final, but this being a rc...
2) before a release (candidate) is called, the release manager need to
be sure that all upstreams are ready. that is; we cannot rely on
unreleased code from dune or ERT. this time, we failed on the ERT
side. luckily, joakim is very responsive.
i understand that for most peeps, calling a release does not come with
anything attached, for the packager, it comes with a very specific
meaning; push out new packages, and push them out asap.
please don't take this as anything but constructive input, i'm not
whining ! :)
-------------------
issues encountered pushing out packages;
0) eigen3 is a b**** to package on launchpad but it's done.
1) opm-autodiff had a failing test. in the interest of pushing out the
test release, i have disabled this test in the packages. i will
investigate the cause before the final. the maintainer is already
informed.
2) not entirely unexpected, but the new packages have some issues.
opm-material does not produce documentation, opm-verteq is missing a
forgot one detail; while not explicitly mentioned i took the liberty of
assuming opm-polymer has not gotten the boot and is still part of the
release. if this is not the case, please confirm before the final.
arnem
_______________________________________________
Opm mailing list
[email protected]
http://www.opm-project.org/mailman/listinfo/opm
