semantic-versioning

问题 In semantic versioning the general rule is to increase the minor number only when backwards compatible functionalities are introduced, otherwise the major number must be increased instead. The same approach, but with a different arithmetic, is used by libtool . I have a question concerning what is considered a backwards compatible change and what not. Imagine I have written a library, and the public header of this library contains a typedef of a data type named foo . In version 1.0.0 this

问题 We use the wonderful semantic versioning paradigm when versioning our rails app. One question I had was where is it best to store this number? I've seen it stored in /lib , environment.rb , etc. Just wondering what people thought as to best practices? 回答1: I don't really think there's any convention for this. I guess it's all about what seems natural to you. Some places the version number can be placed are in: config/environment.rb config/application.rb config/initializers/version.rb by

问题 Bower enables me to specify version requirements for packages using the following syntax: "dependencies": { "<name>": "<version>", }, But I have not been able to find what is the syntax to use for the <version> . I know that I can specify versions to be: greater than a certain version with ">1.0.0" greater than or equal to a version: ">=1.0.0" or in some range: "1.0.0 - 2.0.0" . I also know that there is a common version syntax containing the tilde: "~1.0.0" . But I am not sure what it means

问题 Some time ago I had asked whether adding fields to a struct of a shared library would require a major or a minor change in the version string according to semantic versioning. The few participants where inclined to suggest a major change. Months have passed and I have not added any fields to my struct yet. But now it might be the right time for doing it. However in the meanwhile I have also been thinking about how this could break binary compatibility with programs compiled with previous

问题 Using the semver NPM package https://docs.npmjs.com/misc/semver is there a way to convert a package version like so ^4.2.3 , to one that is without the ^ ? I just need to do string manipulation to remove any preceding characters that are not numbers, I suppose. 回答1: Ah yes, the answer is in the docs, of course: https://docs.npmjs.com/misc/semver it says: semver.clean(' =v1.2.3 ') // '1.2.3' 来源： https://stackoverflow.com/questions/48348948/use-semver-package-to-convert-4-2-3-to-4-2-3

问题 SUMMARY How do I create a publisher policy assembly that targets the same framework version as the redirected assembly? TL;DR I have an Assembly.dll with version 1.x.y.0 and I also have a publisher policy for it named policy.1.0.Assembly.dll which redirects versions 1.0.0.0-1.x.y.0 to 1.x.y.0 . The Assembly.dll targets .NET Framework 3.5. Am I right in thinking that the policy.1.0.Assembly.dll should also target .NET Framework 3.5 for things to work correctly on all frameworks 3.5+? If yes,

问题 I maintain an AngularJS library called Angular Modal Service. I would like to change the dependencies so that I target AngularJS 1.3, like this: "dependencies": { "angular": "~1.3.0" } However, I know categorically that the library works for ~1.2. I don't want to force consumers who want the latest version of my code to have to upgrade, it is possible to do this: "dependencies": { "angular": "~1.3.0 | ~1.2.0" } Letting my library remain low impact? And if it is possible, is it in fact

问题 I've been reading up on all the approaches to version REST APIs. In almost all implementations, controllers and views are versioned, however models are not. To give the rails example, controllers are organized as: # app/controllers/api/v1/events_controller.rb class Api::V1::EventsController < Api::ApiController end Corresponding views as put in at different versioned directories as well. Why don't we version models? Is it because we expect our model (underlying database schema) to not change

问题 Normally a bower.json file specifies some dependencies, but these are typically expressed so that they allow a range of versions of a bower package to be used (e.g. >=1.0 , which means anything higher than version 1.0). I have an automated process which needs to find what version of a bower package is actually installed on this system right now. How can I find this out programmatically (just the version itself), ideally using standard Unix command line tools / the bower command? bower info

问题 When I set my TFS 2015 build definition, that is creating a NuGet package, I set the Build Number format with: $(BuildDefinitionName)_$(Major).$(Minor)$(rev:.r) Where Major and Minor or just variables that I defined. When I use the step "NuGet Packager", I get the error: Could not find version number data in BUILD_BUILDNUMBER. When I use 4 digits, I don't get the error. How do I get it to work with semantic versioning? 回答1: I found the solution: 1) You need to get access to your Build Agent