From and at poware.org  Tue Apr 11 09:25:02 2017
From: and at poware.org (Andreas Lauser)
Date: Tue, 11 Apr 2017 11:25:02 +0200
Subject: [Opm] Reminder: Feature merge cutoff
Message-ID: <7209980.l5ZdrsdSOJ@singularius>

Hi,

This is just a reminder that the cutoff date for potentially disruptive 
merges into the master branches of all OPM modules that are involved in the 
2017.04 release is today. You may pick the time zone of your choice.

The master branches will be fully frozen for feature merges tomorrow and 
Thursday until release branches will be created, and they will stay "sluggish" 
until the release has been finalized. I may make an exception for PRs which are 
nominated in response to this e-mail, but only if these PRs are already open.

cheers
  Andreas

-- 
Just because a patch doesn't solve world hunger isn't really a good
reason to reject it.
        -- Daniel Vetter
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: This is a digitally signed message part.
URL: <//opm-project.org/pipermail/opm/attachments/20170411/26789be6/attachment.sig>

From and at poware.org  Thu Apr 13 11:15:13 2017
From: and at poware.org (Andreas Lauser)
Date: Thu, 13 Apr 2017 13:15:13 +0200
Subject: [Opm] The 2017.04 release branches have been created
Message-ID: <3185729.vhf2xkPnd5@singularius>

Hi,

I have just created and uploaded the stable branches of OPM 2017.04 for all 
modules featured by this release. They are called "release/2017.04" and are 
fairly close to what the final release will look like, i.e., these branches are 
supposed to only get fixes for serious bugs and packaging updates. For this 
reason, Arne Morten Kvarving is the person in charge of them. That said, 
maintainers are responsible to apply all bugfixes from the master branch to the 
release branch and vice versa until the final version have been made; i.e., if 
maintainers decide to merge disruptive changes to master, that's okay with me, 
but I'll grill them if they do not fix corresponding bugs in the release branch 
via minimal patches, so I advice to be a bit conservative with pressing The 
Green Button (TM) during the next two weeks or so.

cheers
  Andreas

-- 
Just because a patch doesn't solve world hunger isn't really a good
reason to reject it.
        -- Daniel Vetter
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: This is a digitally signed message part.
URL: <//opm-project.org/pipermail/opm/attachments/20170413/2c26d330/attachment.sig>

From Arne.Morten.Kvarving at sintef.no  Tue Apr 18 13:05:49 2017
From: Arne.Morten.Kvarving at sintef.no (Arne Morten Kvarving)
Date: Tue, 18 Apr 2017 13:05:49 +0000
Subject: [Opm] The 2017.04 release branches have been created
In-Reply-To: <3185729.vhf2xkPnd5@singularius>
References: <3185729.vhf2xkPnd5@singularius>
Message-ID: <AM5PR0602MB3235F268C32C74294FCEB7DAD9190@AM5PR0602MB3235.eurprd06.prod.outlook.com>

The testing ppa is now populated with rc1 packages for ubuntu xenial. rc1 has been tagged in all repos, and backports of updates have been submitted.


i didn't get explicit instructions on whether to build for trusty or not, so i took the "lazy" decision. if you want those packages as well, just say so.


TLDR;lock on release branches lifted. commence backport activities.

________________________________
Fra: Opm <opm-bounces at opm-project.org> på vegne av Andreas Lauser <and at poware.org>
Sendt: 13. april 2017 13:15:13
Til: opm at opm-project.org
Emne: [Opm] The 2017.04 release branches have been created

Hi,

I have just created and uploaded the stable branches of OPM 2017.04 for all
modules featured by this release. They are called "release/2017.04" and are
fairly close to what the final release will look like, i.e., these branches are
supposed to only get fixes for serious bugs and packaging updates. For this
reason, Arne Morten Kvarving is the person in charge of them. That said,
maintainers are responsible to apply all bugfixes from the master branch to the
release branch and vice versa until the final version have been made; i.e., if
maintainers decide to merge disruptive changes to master, that's okay with me,
but I'll grill them if they do not fix corresponding bugs in the release branch
via minimal patches, so I advice to be a bit conservative with pressing The
Green Button (TM) during the next two weeks or so.

cheers
  Andreas

--
Just because a patch doesn't solve world hunger isn't really a good
reason to reject it.
        -- Daniel Vetter
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <//opm-project.org/pipermail/opm/attachments/20170418/7523d6a6/attachment.html>

From Arne.Morten.Kvarving at sintef.no  Wed Apr 19 12:46:25 2017
From: Arne.Morten.Kvarving at sintef.no (Arne Morten Kvarving)
Date: Wed, 19 Apr 2017 12:46:25 +0000
Subject: [Opm] ResInsight available in ppa
Message-ID: <AM5PR0602MB3235DD475132414716F5A208D9180@AM5PR0602MB3235.eurprd06.prod.outlook.com>

ResInsight 2016.11 is now available in the opm ppa.


It's basically packaged straight out of the resinsight sources, with some minor patchery to properly treat the internal libraries as such (static links so the unix linker doesn't get confused) as well as necessary changes to the packaging files.


sudo apt-get install resinsight


and optionally


sudo apt-get install octave-resinsight for the octave plugins.


arnem
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <//opm-project.org/pipermail/opm/attachments/20170419/1c933429/attachment.html>

From and at poware.org  Mon Apr 24 11:44:57 2017
From: and at poware.org (Andreas Lauser)
Date: Mon, 24 Apr 2017 13:44:57 +0200
Subject: [Opm] Packages for the second release candidate of OPM 2017.04
	available
Message-ID: <9338887.NmWIqi1ST0@heuristix>

Dear OPM community,

On behalf of the release team, I'm happy to announce that packages of the 
second release candidate of the upcoming OPM 2017.04 release are available for 
Ubuntu 16.04:

https://launchpad.net/~opm/+archive/ubuntu/testing/

If no release critical issues will be found, the software contained packages 
will be identical to the final version.

Have Fun
  Andreas



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part.
URL: <//opm-project.org/pipermail/opm/attachments/20170424/dabf6acd/attachment.sig>

From and at poware.org  Wed Apr 26 16:42:17 2017
From: and at poware.org (Andreas Lauser)
Date: Wed, 26 Apr 2017 18:42:17 +0200
Subject: [Opm] Version 2017.04 of the OPM simulation software suite has been
	released
Message-ID: <2133332.vc84l9rPvh@heuristix>

Dear OPM community,

The Open Porous Media project is glad to announce that version 2017.04 of the 
OPM suite of simulation software has been released:

http://opm-project.org/?p=890

Installation instructions can be found on our download page:

http://opm-project.org/?page_id=36

Certainly the most significant change of this release cycle is the introduction 
of the "flow_ebos" simulator. Compared to the previous "flow" simulators, 
"flow_ebos" uses a different approach to linearize the non-linear system of 
partial differential equations and for this reason exhibits significantly 
better performance. The new simulator is intended to eventually fully replace 
the current family of simulators (i.e., "flow", "flow_mpi", "flow_solvent",  
"flow_polymer", etc.) and unify them under the name "flow". Also, it should 
already provide a proper superset of the capabilities of the "flow" simulator 
of previous OPM releases and for this reason, the name "flow" has been made an 
alias for "flow_ebos" in OPM 2017.04. If, for some reason, the previous 
simulator must be used, it is still shipped as "flow_legacy" in this release, 
but we strongly encourage you to send us bug reports if you encounter any case 
that can be simulated using "flow_legacy" but not using the new "flow" 
simulator.

Besides the introduction of "flow_ebos", plenty unit tests have been added, a 
plethora of bugs has been fixed, well handling has been considerably improved 
and now supports e.g. top-hole pressure controls and vertical flow performance 
tables, ECL output and restart capabilities have been made much more 
comprehensive, and all grid related functionality of opm-core has been moved 
to the opm-grid module in preparation of the former module's eventual 
retirement. In addition, a Docker container has been uploaded to Docker Hub to 
ease deployment for people who are interested in container technologies.

Last but not least, I would like to thank everyone who contributed to making 
the many changes of this release happen so smoothly. It has been a pleasure to 
work with you!

Have fun with the new toy!
  Andreas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part.
URL: <//opm-project.org/pipermail/opm/attachments/20170426/4f5e0625/attachment.sig>