16 Matching Annotations
  1. Sep 2021
    1. My understanding is that the caret is the answer for traditional SemVer, i.e., there will be breaking changes prior to 0.1.0, there may be breaking changes between minor versions prior to 1.0.0, and there may only be breaking changes between major versions above 1.0.0.
  2. Aug 2021
    1. The TypeScript team has made it clear. They do not follow semver. "minor" (X.X) releases can contain breaking changes. Major releases (X) have very little meaning.
  3. Dec 2020
  4. Nov 2020
    1. Adapters are strictly versioned: any change to an adapter interface - associative or not - is considered breaking and will cause a major version update of the component.
    1. I feel that with all that power that it’s gaining, instead of being a more approachable tool, that it’s actually being a tool that is continuously making people feel frustrated, to the point where I feel that whatever the next version control system is… (And it does not have to be something separate than Git. It should maybe be just a really powerful abstraction built on top of Git.) But I think whatever the next iteration of the people’s version control is… it should be something that is more reflective of how we think about what version control is for us.
  5. Oct 2020
  6. Sep 2020
    1. The versions must be compatible, so if a peerDependency is listed as 2.x, you can’t install 1.x or another version. It all follows semantic versioning.
  7. Apr 2020
  8. Jan 2020
  9. Nov 2018
  10. Jun 2018
    1. Barbary K. 2014 sncosmo Zenodo, 10.5281/zenodo.11938

      This software citation losts its version information. We will have to work on our typsetting and production rules, as well as develop formal JATS/NLM XML schema to contain versioning information.

  11. Oct 2017
  12. May 2015
    1. I'm a big fan of the approach that Stripe has taken to API versioning -

      Ouch ! :/ I read somewhere else that this was in fact very bad practice...