A reminder!
Currently I see the following MRs with v3.17-release milestone
Satish
---
Cleaning up some Plex I/O
!5013 · created 2 days ago by Matthew Knepley v3.17-release
Change a bunch of PetscCheckFalse() to PetscCheck() in pc
!5000 · created 3 days ago by Barry Smith v3.17-release
Support COO for MatHypre
!5023 · created 10 hours ago by Junchao Zhang v3.17-release
Plex: Enhance extrusion
!5019 · created 21 hours ago by Matthew Knepley v3.17-release
Draft: SNES: delete empty examples 0 of 2 tasks completed
!5024 · created 4 hours ago by Vaclav Hapla v3.17-release
PetscSection: Lazy maxDof calculation.
!5025 · created 3 hours ago by Vaclav Hapla v3.17-release
Mat_MPIAIJCUSPARSE does not need to have its own stream or cuSparse handle
!5020 · created 17 hours ago by Junchao Zhang v3.17-release
Draft: configure: update packages for 3.17.0
!4982 · created 1 week ago by Pierre Jolivet v3.17-release
Draft: release: set petsc v3.17.0 strings
!5015 · created 1 day ago by Satish Balay v3.17-release
Remove use of PetscCheckFalse() on a subset of examples
!5006 · created 2 days ago by Barry Smith v3.17-release
dmnetwork rebalance vertices
!4945 · created 2 weeks ago by Getnet Betrie v3.17-release
On Thu, 3 Mar 2022, Satish Balay via petsc-dev wrote:
> All,
>
> Its time for another PETSc release - due end of March.
>
> For this release [3.17], lets work with the following dates:
>
> - feature freeze: March 28 say 5PM EST
> - release: March 30 say 5PM EST
>
> Merges after freeze should contain only fixes that would normally be
> acceptable to "release" work-flow.
>
> I've created a new milestone 'v3.17-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
>
