brodybits opened a new pull request #454: Mark 7.1.1-dev via coho
URL: https://github.com/apache/cordova-android/pull/454
 
 
   <!--
   Please make sure the checklist boxes are all checked before submitting the 
PR. The checklist
   is intended as a quick reference, for complete details please see our 
Contributor Guidelines:
   
   http://cordova.apache.org/contribute/contribute_guidelines.html
   
   Thanks!
   -->
   
   ### Platforms affected
   
   Android
   
   ### What does this PR do?
   
   Set version to `7.1.1-dev` in `7.1.x` branch via cordova-coho
   
   NOTE: I had to use special version of cordova-js with node_modules committed 
(<https://github.com/apache/cordova-js/commit/f5a790b434f6ac050da55c57e5fd5770f5a16512>
 in 
<https://github.com/apache/cordova-js/tree/cb-4.2.3-node-modules-for-coho-only>,
 see also <https://github.com/apache/cordova-js/pull/156>) in order to get 
cordova-coho to work for me. I also used a couple local modifications to 
cordova-coho to get it to work for me. I really hope to see a better solution 
coming in the future, hope to find time to take a closer look someday.
   
   ### What testing has been done on this change?
   
   --
   
   ### Checklist
   
   - ~~[Reported an issue](http://cordova.apache.org/contribute/issues.html) in 
the JIRA database~~
   - ~~Commit message follows the format: "CB-3232: (android) Fix bug with 
resolving file paths", where CB-xxxx is the JIRA ID & "android" is the platform 
affected.~~
   - ~~Added automated test coverage as appropriate for this change.~~

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


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to