Hi Satish, I'm working on right now on some edits to part of the "Performance Turning" part of the manual. If I can get these edits to a state I'm happy with, I'd like them to go in the release, but I'm not sure if I will have them ready before this evening. --Richard On Thu, Apr 5, 2018 at 5:58 AM, Balay, Satish <[email protected]> wrote:

All,

master builds have been clean for the past 2 days [except for some timeouts]

http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/ 2018/04/04/master.html

However next is still not clean [slightly better than previous build]

http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/04/05/next.html

[i.e the following branches still need fixes]

...

origin/knepley/fix-dm-gmg origin/knepley/fix-ex62-tests origin/knepley/fix-fe-bd-integral origin/knepley/fix-fe-vector-spaces origin/knepley/fix-snes-ex69 origin/tisaac/feature-dmfield

I have the following branches in queue for master [via next-tmp - these builds will start soon]

origin/balay/update-petsc4py-pre-39 origin/dalcinl/mat-getset-ops origin/jczhang/fix-vecscatter-msg-logging

If next-tmp is clean - I can spin the release tarball later today [after merging them to master]

Or if there are other branches [that are clean] - that should go into release - let me know. We'll either have to wait one more day [for these branches to go through next/next-tmp - or I can schedule another next-tmp build later today (with additional branches) - if they are ready by 3:30pm CST]

If I do not hear back about additional branches, and next-tmp is clean - will spin the release tarball later today.

Thanks, Satish