[GitHub] [mynewt-newt] ccollins476ad opened a new pull request #313: [DO NOT MERGE] During install / upgrade, if the requested commit doesn't exist, try to check out the latest "rc" tag instead

[GitBox <gi...@apache.org>]

ccollins476ad opened a new pull request #313: [DO NOT MERGE] During install / upgrade, if the requested commit doesn't exist, try to check out the latest "rc" tag instead
URL: https://github.com/apache/mynewt-newt/pull/313
 
 
   # DO NOT MERGE: This PR includes another PR (https://github.com/apache/mynewt-newt/pull/312).  That one should be merged first.
   
   During install / upgrade, if the requested commit doesn't exist, try to check out the latest "rc" tag instead.  This behavior is useful when a release candidate is being tested.  In this case, the "rc" tags exist, but the official release tag has not been created yet.
   
   ## Example:
   
   ```
   ### project.yml
       repository.apache-mynewt-core:
           type: git
           vers: 2.0.0
           url: 'git@github.com:apache/mynewt-core.git'
   
   ### repository.yml (mynewt-core)
       repo.versions:
           "2.0.0": "mynewt_2_0_0_tag"
   ```
   
   The `mynewt_2_0_0_tag` doesn't actually exist yet.  This tag will not get created until 2.0.0 is actually released.  However, the following tags do exist:
   
   * `mynewt_2_0_0_rc1_tag`
   * `mynewt_2_0_0_rc2_tag`
   
   When newt attempts to upgrade, upon discovering that the requested tag does not exist, it uses the latest "rc" tag instead (rc2 in this case).  If an "rc3" tag is later added, then the next upgrade operation will check out the new tag.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services