[petsc-dev] petsc release plan for march 2021

[Patrick Sanan]

I added that milestone to some of the current docs MRs but it’s probably
too tight, so I suggest to remove - it probably doesn’t matter much what’s
in the tar all for docs so safer to have the current docs. We could have a
patch release which updates the docs for release, once we’re happy with the
docs build on main.

Satish Balay via petsc-dev <petsc-dev at mcs.anl.gov> schrieb am So. 28. März
2021 um 20:58:

> Perhaps I should not have kept a weekend deadline here.
>
> Lets use 'freeze': 'March 29 (Mon) 5PM CST' - but retain the release date
> 'March 30 5PM EST (we have March 31 - if needed)
>
> Satish
>
>  On Sun, 28 Mar 2021, Satish Balay via petsc-dev wrote:
>
> > A reminder!
> >
> > Satish
> >
> > On Tue, 9 Mar 2021, Satish Balay via petsc-dev wrote:
> >
> > > All,
> > >
> > > Its time for another PETSc release - due end of March.
> > >
> > > For this release [3.15], will 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 workflow.
> > >
> > > I've created a new milestone 'v3.15-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
> > >
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20210329/0981c537/attachment.html>