[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
CONTRIBUTE and where to commit bug fixes
From: |
Michael Heerdegen |
Subject: |
CONTRIBUTE and where to commit bug fixes |
Date: |
Fri, 07 Sep 2018 02:56:23 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) |
Hello,
As an occasional contributor I'm often unsure about to which branch a
bug fix or change should be committed to. In CONTRIBUTE we have this
paragraph:
| If you are fixing a bug that exists in the current release, be sure to
| commit it to the release branch; it will be merged to the master
| branch later by the gitmerge function.
but that's obviously not always true: depending on the release cycle,
only fixes for bugs that where introduced in the last release are
accepted, or even less. And if a fix is not ok for the release branch
in a moment, should it go to master, or should it just wait until
later?
So - could we enhance the quoted paragraph? As it is I find it
misleading.
How can I find out which fixes are acceptable for the release branch at
any moment without asking every time? I'm already following emacs-dev
but still sometimes find difficult to answer this question. I couldn't
exactly say what the current policy is for example.
Thanks,
Michael.
- CONTRIBUTE and where to commit bug fixes,
Michael Heerdegen <=