[petsc-dev] Target next PETSc/TAO release for March 30

[Karl Rupp]

Hi Stefano,


> Next is quite messy at the moment. How are we going to handle merging to 
> master? I have a couple of branches that are sitting in next for a 
> while, and that can be merged safely 
> : stefano_zampini/fix-matis-dmda-l2g and stefano_zampini/add-pod-test

I merged stefano_zampini/add-pod-test to master.

stefano_zampini/fix-matis-dmda-l2g has two commits that are not in next. 
The latest one says "still does not work properly", hence I don't think 
it's a good idea to merge to master right away... ;-)

Best regards,
Karli


> 
> Il 23 Mar 2018 8:21 PM, "Jed Brown" <jed at jedbrown.org 
> <mailto:jed at jedbrown.org>> ha scritto:
> 
>     I think it's feasible, but are we ever going to have more than a week's
>     notice so that we can have a known merge window followed by a few days
>     of feature freeze?
> 
>     Richard Tran Mills <rtmills at anl.gov <mailto:rtmills at anl.gov>> writes:
> 
>      > All,
>      >
>      > To meet deliverables for one the DOE projects providing major
>     funding for
>      > PETSc development, Barry, Todd, and I agree that we should target
>     Friday,
>      > March 30 for the next PETSc/TAO release.
>      >
>      > Does anyone see any major obstacles to this? Does anyone have
>     anything that
>      > will require some extra help/coordination?
>      >
>      > Thanks,
>      > Richard
> 
>