[petsc-dev] Schedule for next release

[Smith, Barry F.]

  Note that we will be switching to Gitlab CI during the early part of the time frame and this will slow down (stop) the pull request process at times.

  To help the process, everyone could try to do more testing before submitting a pull request. Run with all combinations of complex/real, precisions, languages, 64 bit indices, external packages and compilers.

 1)  Also everyone should get gitlab ids and set their ssh keys NOW. 
 2) please try when possible to use the same id as on bitbucket and 
 3)  please use your picture  so that everyone will immediately recognize as them so we have an easy time associated the right people
 4)  please send me your gitlab ids and emails so we can quickly get the right invitations out and set up permissions. 
 5) It is possible to somehow use gitlab with your GitHub credentials so if you prefer to do that I think it should be fine.

There will be a bit of scurrying around as we change to gitlab and the better prepared we are the better things will go.


   Barry


> On Aug 14, 2019, at 6:25 AM, Karl Rupp via petsc-dev <petsc-dev at mcs.anl.gov> wrote:
> 
> Hi all,
> 
> let me propose the following schedule for the next release:
> 
> * until Sunday, September 15: New pull requests are considered for the upcoming release.
> 
> * from Monday, September 16, to Sunday, September 22: Fixing and merging of open pull requests received by September 15. Extended testing of `master`. Simple bug-fix pull requests are still considered.
> 
> * from Monday, September 23: Satish spins the release as soon as all fixes are in.
> 
> With this schedule we will have a release by the end of September. The 'merging period' is shorter than for previous releases, because the pull request workflow requires less bugfixing right before the release.
> 
> Satish, does this schedule work for you? Or should we move everything forward by one week?
> 
> Any comments are of course welcome.
> 
> Best regards,
> Karli