11 ms·
Curious; have they made any statements on their versioning? I've seen mature projects years in development that are still 0 for major and in the teens for the m
by Negative1 10y ago
Curious; have they made any statements on their versioning? I've seen mature projects years in development that are still 0 for major and in the teens for the minor version. Despite breaking changes Swift is now a 3.0 project?
- AsyncAwait 10y agoI've come to the conclusion that is because Apple can't release anything that may not look (on paper) as being "ready", since they built their image on attention to detail and polished products - so in other words, a Swift 0.x. would not have seem polished/professional enough for Apple to release into the wild, even if it had all the present functionality.
- natthan 10y agoI believe that they are using Semantic Versioning 2.0.0[1] as discussed in the Swift Package Manager Project's Website[2] under "Importing Dependencies": > Given a version number MAJOR.MINOR.PATCH, increment the: > MAJOR version when you make incompatible API changes, > MINOR version when you add functionality in a backwards-compatible manner, and > PATCH version when you make backwards-compatible bug fixes. > Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format. [1] Semantic Versioning 2.0.0 http://semver.org http://semver.org [2] Swift.org - Package Manager https://swift.org/package-manager/ https://swift.org/package-manager/
- deleted 10y ago[deleted]