Timeline for How does a software engineer version two minor updates at the same time?
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 16, 2020 at 10:01 | history | edited | CommunityBot | Commonmark migration | |
| Jul 18, 2019 at 15:19 | vote | accept | Marvin | ||
| Jul 17, 2019 at 20:04 | comment | added | gregmac | Where SemVer could come into play with a web api is the actual public REST/SOAP/GraphQL/whatever API, if there is one, but in that case the API version is actually separate from the application version, because usually you'd keep older version APIs accessible for quite a while. This is essential to allow developers consuming that API to update and deploy their own apps on their own frequency. As far as SemVer + web APIs, I'd say only the major.minor version matters, and in many cases it's just major -- as an API consumer, I just don't want my app to break when you deploy an update. | |
| Jul 17, 2019 at 19:52 | comment | added | gregmac | If you're doing a single deployment web app (eg, you don't have users hosting their own versions of your app) then the version number of the app itself becomes really unimportant. It's good to have a district number so you can identify what code is running on your server (useful for troubleshooting), but none of your users will care. Do whatever you like that's easy to track. Personally for apps like that, I usually just have 1.0.build_number where build_number is just the auto-increment number my CI server generates on every build. | |
| Jul 17, 2019 at 19:03 | comment | added | Marvin | So it should become 0.10.0? | |
| Jul 17, 2019 at 19:01 | comment | added | Paul | I'm not understanding your comments @Marvin, the answer is that the number of features you add/change/remove in the release doesn't affect the release number, regardless of how significant or distinct the features are. Have you looked at SemVer'd opensource projects? They typically have a changelog that shows the (often many) changes that are encapsulated in a single release. | |
| Jul 17, 2019 at 18:34 | comment | added | Marvin | Also, this is a web app so the users do not upgrade, it automatically updates for them when I upload all the files to the public server | |
| Jul 17, 2019 at 16:13 | comment | added | Marvin | These are two distinct features, but you advised to only increment by one. Since I am still in pre-release, I release every week. The day has not come where I release again, and because I will continue this organized procedure of releasing, I will have both distinct features finished by the next release date. | |
| Jul 17, 2019 at 15:52 | history | edited | gregmac | CC BY-SA 4.0 | add TLDR |
| Jul 17, 2019 at 3:15 | history | answered | gregmac | CC BY-SA 4.0 |