On a module Issue page, how do you tell what version the patch has been applied in?

Question

Much of the time, take this field collection migration issue for example, when I find an issue with a drupal module, there has already been an issue filed, and in some cases the issue has a status of Closed (fixed). In the sidebar there is a version mentioned. It seems likely that that version is the one you set when you file the issue, specifying which branch of the code you saw the issue in.

When the issue has been Closed (fixed), does that mean that if you grab the specified version, that the code will include the patch? Is there any way of knowing when a fix has reached the stable branch?

Answer 1

As mentionned by Eyal a patch is always applied to the -dev version of the module. That's already a good stuff to know. So yes, if a patch is committed you can download the -dev version specified in the issue (or apply the patch separately if needed).

Usually the patches included in a new release are listed in the changelog: .

note: normally once a patch is committed the issue status becomes "closed (fixed)" and you will ind this kind of details in the latest issue comments:

In the sidebar of the presentation page of the module the "View pending patches" can be helpful to check if the issue you are looking for is still opened or fixed. There is also the "Views commits" link for a quick overview. this page provides a detailed list of the patches implemented (issue date, version , description, id).

--

The official doc https://www.drupal.org/issue-queue/status could also help you to understand the process.

Answer 2

Patches are not always applied to the dev branch. This is not the case always although it would be. For example there may be 2.x and 1.x version or maybe the stable release is 1 year ahead from the dev branch etc.

The official rules for submitting patches can be found here: Submitting patches.

In reality the patches refer to the version (release or branch) that issued the patch. See the example. And the naming rules say that you should add the project branch in the patch name too!

When you create an issue on D.O. you are obligated to enter the project version that issued the issue. So any patches submitted there refer to the "version of the issue". When the branch is the dev branch which changes often the patch need to change often too! That's why you see so many patches for an issue if it is not closed soon.

Also, D.O. has a special bot that takes patches from issues and apply them to the project so every patch has a pass status. See more at Drupal.org Testbots.

D.O. : Drupal.org