People,

Since very early in the project we had maintained the standard that any PR
will need
- two reviews
- at minimal one review containing a test report
We also stated some exception;
- text only changes
- changes to test code
- changes to ci code
Lately, mostly with the involvement of storage vendors we had let that go.
I remember that we would allow PRs that need specific hard- or software, if
the vendor would add a test report to their own PR (citation needed!)

Now there are two amendment that I want to make to that practice:
- I want formulising it in some textual form in our git repo.
- I want to add that users that tested their own code can merge it if after
a period of four weeks nobody else tested it to prove some flaw and made an
objection.

Especially the last one is a significant change. The intention is for users
to be able to get through the large backlog we have and have fixes and
enhancements that are vital to them merged.

thoughts?

regards,

Reply via email to