Disambiguate and document the merge/close process

[Basil Crow]

Over the past few months and especially during Hacktoberfest, I have
observed several cases where the Jenkins core contribution process did
not go as smoothly as it could have gone. After thinking deeply about
several examples, I concluded that the existing process contains
several ambiguities that, once disambiguated, would make the process
go more smoothly in the future. I distilled my thoughts into a
concrete process improvement in
https://github.com/jenkinsci/jenkins/pull/7516 and submitted my
proposal for review in December.

Response to this proposal has been mostly positive, with negative
feedback isolated to specific details of the proposal rather than the
overall concept. All feedback has been addressed at the present time.

I would like to bring this proposal to a conclusion by March. If any
active core maintainers have not yet considered the proposal, please
do so and express (in the pull request) your view — positive,
negative, or neutral — and the reason for that view. If anyone has
left feedback already, please confirm that it has been addressed in
the latest revision by approving the pull request.

[Oleg Nenashev]

Thanks for working on it, Basil! I think the pull request documents the current process well, and I support merging it in the current form

[Basil Crow]

On Thu, Feb 9, 2023 at 4:54 PM Basil Crow <m...@basilcrow.com> wrote:
>
> I would like to bring this proposal to a conclusion by March.

https://github.com/jenkinsci/jenkins/pull/7516 has been approved; if
nobody objects by March 15, I'll assume lazy consensus and merge it.