Is your proposal related to a problem?
As a contributor, I see three places how contributing can be less frustrating:
- Release bug fixes in a patch release.
- Release fixes from the pull request sooner.
- If it is not possible, give explain the problem to the contributor.
My recent small bugfix PR can be an example.
Describe the solution you'd like
As the first suggestion, we can add a rule to always create a branch for major release development. Seems like 4.x development happened in master and was a reason why several PRs waited for a month for release.
Describe alternatives you've considered
But as a person outside of the project, I can miss something. What is the longest step in the current release process? Or maybe there are some psychological blockers (like afraid of multiple issues if patch release will break anything)?
Is your proposal related to a problem?
As a contributor, I see three places how contributing can be less frustrating:
My recent small bugfix PR can be an example.
Describe the solution you'd like
As the first suggestion, we can add a rule to always create a branch for major release development. Seems like 4.x development happened in
masterand was a reason why several PRs waited for a month for release.Describe alternatives you've considered
But as a person outside of the project, I can miss something. What is the longest step in the current release process? Or maybe there are some psychological blockers (like afraid of multiple issues if patch release will break anything)?