Answers.Body: <p>While Github is used for the code collaboration, co-ordination of which issues are fixed in which release is done on over <a href="https://issues.civicrm.org" rel="nofollow">CiviCRM's JIRA install</a>.</p>
  
  <p>In order to better ensure your PR was included in the next <code>4.6.x</code>, you could open an issue there and tag with appropriate versions (eg <code>4.6.10</code> for fix version), then reference the JIRA ticket in the Github PR.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-11-01T23:56:58.190Z
Answers.LastActivityDate: 2015-11-01T23:56:58.190Z
Answers.UserDisplayName: Chris Burgess
Body: <p>I had two pull requests committed to 7.x-master on GitHub over the past year.</p>
  
  <p>When I view the two files that were changed by my pull requests, the changes are present in the master branch.</p>
  
  <p>They do not appear to be included in latest download and I end up having to manually add them.</p>
  
  <p>I was under the assumption that commits to master would be included in future releases.  Is that not the case?</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-11-01T19:10:12.137Z
Comments.Text: My understanding of the branching on github is that the master branch is the next major release. If you want your commit to be at the next minor release. e.g. 4.6.10 then you have to commit it to the 4.6.x branch. In my understanding there is no 7.x-master branch of CiviCRM. See also http://wiki.civicrm.org/confluence/display/CRMDOC/Contributing+to+CiviCRM+using+GitHub
Comments.UserDisplayName: Jaap Jansma - CiviCooP
Tags: <upgrade>
Title: Why are commits to 7.x-master not included in latest versions of CiviCRM?
ThreadText: # Why are commits to 7.x-master not included in latest versions of CiviCRM?
  
  (Asked by: username_0 on 2015-11-01)
  
  I had two pull requests committed to 7.x-master on GitHub over the past year.
  
  When I view the two files that were changed by my pull requests, the changes are present in the master branch.
  
  They do not appear to be included in latest download and I end up having to manually add them.
  
  I was under the assumption that commits to master would be included in future releases. Is that not the case?
  
  **Tags:** upgrade
  
  > **Comments:**
  > **username_1**: My understanding of the branching on github is that the master branch is the next major release. If you want your commit to be at the next minor release. e.g. 4.6.10 then you have to commit it to the 4.6.x branch. In my understanding there is no 7.x-master branch of CiviCRM. See also http://wiki.civicrm.org/confluence/display/CRMDOC/Contributing+to+CiviCRM+using+GitHub  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2015-11-01. Score: 1 | Accepted answer
  
  While Github is used for the code collaboration, co-ordination of which issues are fixed in which release is done on over [CiviCRM's JIRA install](https://issues.civicrm.org).
  
  In order to better ensure your PR was included in the next `4.6.x`, you could open an issue there and tag with appropriate versions (eg `4.6.10` for fix version), then reference the JIRA ticket in the Github PR.
  
  
  ---
  
  