[petsc-dev] petsc release plan for Sept/2020

[Satish Balay]

A reminder feature freeze is today!

Currently we have:

v3.14-release:

!3250 by Jose E. Roman: Correctly set offload mask in VecCreateSeqCUDAWithArray()
!3251 by Satish Balay: configure: update gitcommit from 'master' to hash [and for branch - usage...
!3137 by Mark: Draft: Adams/feature mat cuda
!2374 by Scott Kruger: Serialize gpu tests through dependency list
!3219 by Junchao Zhang: Add vec Kokkos and mat Kokkos
!3249 by Barry Smith: Improve manual pages for PetscError() and the various error handlers including...
!3191 by Jacob Faibussowitsch: Fortran custom bindings for petsctimsort[witharray]
!3247 by Barry Smith: Do not log transfer time as GPU time. GPU time is used to get performance ON...
!3246 by Barry Smith: Call PetscMallocValidate() on signal and error conditions to check if the...
!3239 by Patrick Sanan Docs: remove old LaTeX-only manual
!3203 by Barry Smith: At GMRES restarts check if the recusion computed residual norm is not...

v3.13-maint:

!2810 by Hong Zhang : Fix autodiff errors due to locked vec
!3149 by Matthew Knepley : Turn on Fortran stub
!3109 by Emil: modified description of ex25 to avoid IMEX confusion.
!3090 by Satish Balay: PETSC_USE_DYNAMIC_LIBRARIES -> PETSC_HAVE_DYNAMIC_LIBRARIES
!3082 by Hong Zhang: Fix docs for TS examples

Satish

On Wed, 2 Sep 2020, Satish Balay via petsc-dev wrote:

> All,
> 
> We are to make a petsc release by the end of September.
> 
> For this release [3.14], will work with the following dates:
> 
> - feature freeze: Sept 27 say 5PM EST
> - release: Sept 29
> 
> Merges after freeze should contain only fixes that would normally be acceptable to maint workflow.
> 
> I've created a new milestone 'v3.14-release'. So if you are working on a MR with the goal of merging before release - its best to use this tag with the MR.
> 
> And it would be good to avoid merging large changes at the last minute. And not have merge requests stuck in need of reviews, testing and other necessary tasks.
> 
> And I would think the testing/CI resources would get stressed in this timeframe - so it would be good to use them judiciously if possible.
> 
> - if there are failures in stage-2 or 3 - and its no longer necessary to complete all the jobs - one can 'cancel' the pipeline.
> - if a fix needs to be tested - one can first test with only the failed jobs (if this is known) - before doing a full test pipeline. i.e:
>    - use the automatically started and paused 'merge-request' pipeline (or start new 'web' pipeline, and cancel it immediately)
>    - now toggle only the jobs that need to be run
>    - [on success of the selected jobs] if one wants to run the full pipeleine - click 'retry' - and the remaining canceled jobs should now get scheduled.
> 
> thanks,
> Satish
>