[petsc-dev] PETSc 3.10: September 4, 2018, is the cutoff-date for new features
Satish Balay
balay at mcs.anl.gov
Mon Sep 10 17:02:32 CDT 2018
Also - please check and update src/docs/website/documentation/changes/dev.html as needed.
Thanks,
Satish
On Wed, 5 Sep 2018, Karl Rupp wrote:
> Dear PETSc developers,
>
> please open any outstanding pull requests for the upcoming PETSc 3.10 release
> in the next few hours. After that, please do not merge anything to `next` or
> `master` unless it is integration work for existing open PRs.
>
> You can open up new pull requests in the next days and weeks as usual. If
> these are documentation enhancements, we will most likely integrate them
> quickly. If these are bugfixes, we may still integrate them for PETSc 3.10,
> decided on a per-case basis. New features, however, will not be integrated
> until PETSc 3.10 is out.
>
> Thanks and best regards,
> Karli
>
>
>
> On 08/30/2018 06:09 PM, Karl Rupp wrote:
> > Dear PETSc developers,
> >
> > this is a gentle reminder for the cutoff-date on September 4.
> >
> > Best regards,
> > Karli
> >
> >
> >
> > On 07/27/2018 02:41 AM, Karl Rupp wrote:
> >> Dear PETSc developers,
> >>
> >> in order to ensure a PETSc 3.10 release no later than by the end of
> >> September (possibly earlier), we agreed on September 4, 2018, as the
> >> cut-off date for new features. Please make sure that a pull request has
> >> been opened on Bitbucket by this time. This is the preferred model over
> >> merging to next directly, since our Jenkins test infrastructure will test
> >> each PR separately (thus providing faster feedback and thus allow for
> >> faster integration).
> >>
> >> And while we are at it: Please keep in mind that new features also require
> >> appropriate documentation. :-)
> >>
> >> Thanks and best regards,
> >> Karli
>
More information about the petsc-dev
mailing list