[petsc-dev] petsc release plan for march/2020

[Jed Brown]

Satish Balay <balay at mcs.anl.gov> 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 everything we had intended to
>> get in this release?  I feel like we should ping those merge
>> requests/issues asking people to either commit to completing them or
>> defer to post-release.
>
> Currently there are about 50 MRs - likely most of them likely inactive.
>
> My thought is to make the default 'mater' (i.e post release) - and use 'v3.13-release' for MRs we are actively working for the release. The other way of identifying inactive MRs or the ones not destined for release (and marking them as such) might not be easy. And usually the MR author is the best judge of this (inactive, active for release, active for later). And if active - can easily switch milestore to 'v3.13-release'

Only 19 of which had set the milestone (now called 'master').

> Sure - we should check with MR authors about this. In essence - this e-mail is part of that check.
>
> BTW: I think we should work on getting as many MRs into release as feasible - but not scramble to get everything in.

Yep, agreed.