[petsc-dev] PETSc release by March 29, 2019

[Balay, Satish]

Sure - I would add caveats such as:

- its best to submit PRs early - if they are critical [i.e if the
branch should be in release] - or if they are big - and likely to
break builds.

- we should somehow use both next and next-tmp in a way to avoid some
  PRs clogging the process for others.

  perhaps starting March 18 - freeze access to next - and keep
  recreating next & next-tmp dynamically as needed with the goal of
  testing fewer branches together (ideally 1 branch at a time) - so
  that we can:

   * easily identify the branch corresponding to test failures and
   * easily identify branchs that are ready for graduation.

- We should accept (minor?) bug-fix PRs even after March 22 [i.e
  anything that would be acceptable in our maint work-flow shouldn't
  be frozen]

- And we should be able to drop troublesome PRs if they are blocking
  the release.

Satish

On Tue, 5 Mar 2019, Karl Rupp via petsc-dev wrote:

> Dear PETSc developers,
> 
> let me suggest Friday, March 22, as the cut-off-date for new Pull Requests for
> the upcoming release. This allows for 7 days to iron out any remaining
> glitches. (It only took us a few days to release after the cut-off date last
> September, so this should be fine)
> 
> Also, a clearly communicated cut-off date helps to prevent "may I also squeeze
> this in at the very last minute"-PRs, which I may not have the time to deal
> with anyway.
> 
> Satish, does the above schedule work for you? Since you're creating the
> tarballs, you've got the final word on this :-)
> 
> Best regards,
> Karli
> 
> 
> 
> 
> On 3/4/19 4:31 AM, Smith, Barry F. via petsc-dev wrote:
> > 
> >    Due to ECP deliverables there will be a PETSc release by March 29, 2019.
> > 
> >    Please prepare materials you wish to get into the release soon and check
> > on the progress of your current pull requests to make sure they do not block
> > beyond the release deadline.
> > 
> >      Thanks
> > 
> >       Barry
> > 
> >    If someone would like to propose an intermediate deadline before the 29th
> > for testing/etc purposes please feel free, I don't have the energy or
> > initiative.
> > 
> > 
> >> Begin forwarded message:
> >>
> >> *From: *Jed Brown via petsc-maint <petsc-maint at mcs.anl.gov
> >> <mailto:petsc-maint at mcs.anl.gov>>
> >> *Subject: **Re: [petsc-maint] Release 3.11?*
> >> *Date: *March 3, 2019 at 10:07:26 AM CST
> >> *To: *"Munson, Todd" <tmunson at mcs.anl.gov <mailto:tmunson at mcs.anl.gov>>
> >> *Cc: *petsc-maint <petsc-maint at mcs.anl.gov
> >> <mailto:petsc-maint at mcs.anl.gov>>
> >> *Reply-To: *Jed Brown <jed at jedbrown.org <mailto:jed at jedbrown.org>>
> >>
> >> Can you, or someone else involved at that level, please propose a timeline
> >> on petsc-dev?
> >>
> >> "Munson, Todd" <tmunson at mcs.anl.gov <mailto:tmunson at mcs.anl.gov>> writes:
> >>
> >>> Hi Jed,
> >>>
> >>> Yes, we have a funding milestone due at the end of this month, so we
> >>> should push out a release.
> >>>
> >>> Thanks, Todd.
> >>>
> >>>> On Mar 2, 2019, at 11:36 PM, Jed Brown <jed at jedbrown.org
> >>>> <mailto:jed at jedbrown.org>> wrote:
> >>>>
> >>>> Is there a funding milestone to release 3.11 this month?  If so, we need
> >>>> to publicize a timeline and mention it on petsc-dev?  If not, we can
> >>>> feature release whenever we feel ready, but probably in the next few
> >>>> months.
> > 
>