<div dir="ltr"><div dir="ltr">On Wed, Mar 25, 2020 at 8:23 PM Satish Balay via petsc-dev <<a href="mailto:petsc-dev@mcs.anl.gov">petsc-dev@mcs.anl.gov</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">> > - feature freeze: March 27 say 5PM EST<br>
<br>
A reminder, feature freeze is in 2 days. I see the following MRs with milestone: v3.13-release<br>
<br>
!2598 Add Sphinx docs and port Developers Manual<br>
!2614 Knepley/feature dm remove hybrid<br>
!2626 More support for not needing to set PETSC_DIR yet build with PETSc, also...<br>
!2634 WIP: Balay/release 3.13 revert to dev<br>
!2554 Knepley/feature fe lagrange gll<br></blockquote><div><br></div><div>2554 is not merging. I will change the target.</div><div><br></div><div> Thanks,</div><div><br></div><div> Matt</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
!2367 WIP: Add sample file that demonstrates use of CMake and pkg-config to build a PETSc application<br>
<br>
I'm hoping all v3.13-release MRs will complete testing and reviews (approvals) before the freeze.<br>
<br>
Thanks,<br>
Satish<br>
<br>
On Fri, 20 Mar 2020, Satish Balay via petsc-dev wrote:<br>
<br>
> An update:<br>
> <br>
> <a href="https://gitlab.com/petsc/petsc/-/merge_requests?milestone_title=v3.13-release" rel="noreferrer" target="_blank">https://gitlab.com/petsc/petsc/-/merge_requests?milestone_title=v3.13-release</a><br>
> <br>
> We have a week to go. And have about 47 MRs, with 12 marked as 'v3.13-release' milestone.<br>
> <br>
> Likely the milestone is not correctly set for some MRs - if so - please update the MR.<br>
> <br>
> And I see some MRs with significant code changes. Hopefully we can process them early [and not have large changes close to freeze date].<br>
> <br>
> Satish<br>
> <br>
> On Fri, 13 Mar 2020, Satish Balay via petsc-dev wrote:<br>
> <br>
> > All,<br>
> > <br>
> > We are to make a petsc release by the end of March.<br>
> > <br>
> > For this release [3.13], will work with the following dates:<br>
> > <br>
> > - feature freeze: March 27 say 5PM EST<br>
> > - release: March 29<br>
> > <br>
> > Merges after freeze should contain only fixes that would normally be acceptable to maint workflow.<br>
> > <br>
> > I've changed the current milestone 'v3.13' to 'master' and created a new one 'v3.13-release'<br>
> > <br>
> > If you are working on a MR with the goal of merging before release - its best to use 'v3.13-release' tag with the MR.<br>
> > <br>
> > 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.<br>
> > <br>
> > 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.<br>
> > <br>
> > - if there are failures in stage-2 or 3 - and its no longer necessary to complete all the jobs - one can 'cancel' the pipeline.<br>
> > - 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:<br>
> > - start pipeline<br>
> > - immediately cancel the pipeline<br>
> > - now toggle only the jobs that need to be run<br>
> > - [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.<br>
> > <br>
> > thanks,<br>
> > Satish<br>
> > <br>
> <br>
<br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div>What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead.<br>-- Norbert Wiener</div><div><br></div><div><a href="http://www.cse.buffalo.edu/~knepley/" target="_blank">https://www.cse.buffalo.edu/~knepley/</a><br></div></div></div></div></div></div></div></div>