develwoutacause’s avatardevelwoutacause’s Twitter Archive—№ 1,063

  1. …in reply to @IgorMinar
    @IgorMinar I'm saying it's a coincidence that the accepted abbreviation term for "next prod release" *just happens* to alphabetically follow the accepted convention for general prereleases. Sure, you picked the terms intentionally, but you found a happy medium in a coincidence.
    On twitter.com Twitter logo develwoutacause’s avatar Mood +5 🙂
    1. …in reply to @develwoutacause
      @IgorMinar Imagine if "candidate for release" was the common the term, and cr was the abbreviation. You couldn't use that in combination with next due to alphabetic ordering. You just have to find another term that both: 1. Communicates the intent. 2. Orders alphabetically as desired.
      Permalink On twitter.com Twitter logo develwoutacause’s avatar Mood +2 🙂
      1. …in reply to @develwoutacause
        @IgorMinar Personally, I'd rather see: 1. Prerelease labels are inherently incomparable. 2. Installing ^1.0.0-next.0 can give later patches like 1.0.0-next.1. 3. Installing ^1.0.0-next will *never* give a different label (1.0.0-rc.0).
        Permalink On twitter.com Twitter logo develwoutacause’s avatar Mood +2 🙂
        1. …in reply to @develwoutacause
          @IgorMinar In my mind, the semantics of any given label are defined by the maintainer, and a user of a package has no reason to believe that 1.0.0-foo comes *after* 1.0.0-bar. I don't think it's safe or reasonable for semver to assume an implicit ordering between two such labels.
          Permalink On twitter.com Twitter logo develwoutacause’s avatar Mood 0