[Solr Wiki] Update of "HowToContribute" by ShawnHeisey

[Apache Wiki <wi...@apache.org>]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Solr Wiki" for change notification.

The "HowToContribute" page has been changed by ShawnHeisey:
https://wiki.apache.org/solr/HowToContribute?action=diff&rev1=96&rev2=97

Comment:
Update to reflect current branch reality since branch_4x was removed.

  }}}
  The <branch> part of the command above needs to be replaced by something concrete - the "code line" you want to get.  Examples, and how to interpret what they mean:
  
-  * trunk: Working towards a 5.0 release. This is the main center for development, it's not really a branch.  Releases are never made from trunk, they are only made from the stable development branch.
+  * trunk: Working towards the eventual 6.0 release. This is the main center for development, it's not really a branch.  Releases are never made from trunk, they are only made from the stable development branch.
-  * branches/branch_4x: The current development branch for the next stable 4.x version.
+  * branches/branch_5x: The current stable development branch for the next stable 5.x version.
-  * branches/lucene_solr_4_3: Working towards the latest 4.3.x release. There is never a guarantee that a point release will ever be made after the x.x.0 version is released.
-  * tags/lucene_solr_4_3_0: When a new version is fully released, the lucene_solr_x_x branch is copied to a tag which represents the source code for that specific release.
+  * tags/lucene_solr_4_10_3: When a new version is fully released, the lucene_solr_x_x branch is copied to a tag which represents the source code for that specific release.
+  * branches/lucene_solr_4_10: When branch_4x was removed and 4.x moved to maintenance mode, all 4.x development moved to this branch.  There is never a guarantee that a point release will ever be made after the x.x.0 version is released.
   * branches/lucene_solr_3_6: When branch_3x was removed and 3.x moved to maintenance mode, all 3.x development moved to this branch.
  
  SVN revision numbers can be used to obtain branches and tags from their parents.  For example, revision 1394844 on branches/lucene_solr_4_0 corresponds to the official 4.0.0 release, so if you add "-r 1394844" to the command line above using branches/lucene_solr_4_0 for <branch>, you will get the code corresponding to 4.0.0.  You can also just do a checkout of tags/lucene_solr_4_0_0 to get the same code.
  
- Most development is done on "trunk" and then backported to the other active branches.  At some point in the future, a branch_5x will be created and trunk will be updated to reflect a 6.0 version.  Shortly after that, branch_4x will deleted and bugfixes for 4.x versions will continue on the newest lucene_solr_4_x branch.
+ Most development is done on "trunk" and then backported to the other active branches.  At some point in the future, a branch_6x will be created and trunk will be updated to reflect a 7.0 version.  Shortly after that, branch_5x will deleted and bugfixes for 5.x versions will continue on the newest lucene_solr_5_x branch.
  
  Note that committers have to use [[http://apache.org/dev/committers.html#commit-403|https]] instead of http here, but http is fine for read-only access to the code.
  
- If you prefer you could use the [[https://github.com/apache/lucene-solr|GitHub]] mirror instead. Note that the drop-down lets you select "trunk" or "branch_4x" (among others).
+ If you prefer you could use the [[https://github.com/apache/lucene-solr|GitHub]] mirror instead. Note that the drop-down lets you select "trunk" or "branch_5x" (among others).
  
  == Exporting to a local repository ==
  When making larger scale (please, try to keep your patches as small as humanly possible) changes, or when working in a team, you might want to be able to keep track of what you are doing locally. One way of doing so, is exporting to a local SVN repository.