An update,
I'm ready to spin petsc-3.13.0 tarball with current master [using commits in
balay/release-3.13-revert-to-dev]
Once the tarball is ready - master and maint branches will be updated.
Satish
On Fri, 13 Mar 2020, Satish Balay via petsc-dev wrote:
> All,
>
> We are to make a petsc rel
All,
Please check the changes file - and update any changes/new-features that are
missing from here.
https://gitlab.com/petsc/petsc/-/blob/master/src/docs/website/documentation/changes/dev.html
Thanks,
Satish
On Wed, 25 Mar 2020, Satish Balay via petsc-dev wrote:
> > > - feature freeze: March
Matthew Knepley writes:
> On Wed, Mar 25, 2020 at 9:05 PM Jed Brown wrote:
>
>> Matthew Knepley writes:
>>
>> > On Wed, Mar 25, 2020 at 8:23 PM Satish Balay via petsc-dev <
>> > petsc-dev@mcs.anl.gov> wrote:
>> >
>> >> > > - feature freeze: March 27 say 5PM EST
>> >>
>> >> A reminder, feature f
On Wed, Mar 25, 2020 at 9:05 PM Jed Brown wrote:
> Matthew Knepley writes:
>
> > On Wed, Mar 25, 2020 at 8:23 PM Satish Balay via petsc-dev <
> > petsc-dev@mcs.anl.gov> wrote:
> >
> >> > > - feature freeze: March 27 say 5PM EST
> >>
> >> A reminder, feature freeze is in 2 days. I see the followi
Matthew Knepley writes:
> On Wed, Mar 25, 2020 at 8:23 PM Satish Balay via petsc-dev <
> petsc-dev@mcs.anl.gov> wrote:
>
>> > > - feature freeze: March 27 say 5PM EST
>>
>> A reminder, feature freeze is in 2 days. I see the following MRs with
>> milestone: v3.13-release
>>
>> !2598Add Sph
On Wed, Mar 25, 2020 at 8:23 PM Satish Balay via petsc-dev <
petsc-dev@mcs.anl.gov> wrote:
> > > - feature freeze: March 27 say 5PM EST
>
> A reminder, feature freeze is in 2 days. I see the following MRs with
> milestone: v3.13-release
>
> !2598Add Sphinx docs and port Developers Manual
>
> > - feature freeze: March 27 say 5PM EST
A reminder, feature freeze is in 2 days. I see the following MRs with
milestone: v3.13-release
!2598Add Sphinx docs and port Developers Manual
!2614Knepley/feature dm remove hybrid
!2626More support for not needing to set PETSC_D
An update:
https://gitlab.com/petsc/petsc/-/merge_requests?milestone_title=v3.13-release
We have a week to go. And have about 47 MRs, with 12 marked as 'v3.13-release'
milestone.
Likely the milestone is not correctly set for some MRs - if so - please update
the MR.
And I see some MRs with sig
Satish Balay writes:
>> > Merges after freeze should contain only fixes that would normally be
>> > acceptable to maint workflow.
>> >
>> > I've changed the current milestone 'v3.13' to 'master' and created a new
>> > one 'v3.13-release'
>>
>> Why this way? Is the idea to bulk-offload everyth
On Fri, 13 Mar 2020, Jed Brown wrote:
> Thanks for taking the lead on this, Satish.
>
> Satish Balay via petsc-dev writes:
>
> > All,
> >
> > We are to make a petsc release by the end of March.
> >
> > For this release [3.13], will work with the following dates:
> >
> > - feature freeze: March
Thanks for taking the lead on this, Satish.
Satish Balay via petsc-dev writes:
> All,
>
> We are to make a petsc release by the end of March.
>
> For this release [3.13], will work with the following dates:
>
> - feature freeze: March 27 say 5PM EST
> - release: March 29
>
> Merges after freeze
11 matches
Mail list logo
