Timeline for Why is using build number instead of x.x.x versioning in a web app a bad idea?
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 15, 2016 at 21:35 | comment | added | Andy | The OP doesn't indicate at all that anyone is building anything against his web app. This answer only argues from the point of view of software developers consuming a package, which is not the case, and so isn't very compelling. | |
| Jul 15, 2016 at 21:06 | comment | added | pllee | This answer makes perfect sense for any publicly consumed library but doesn't help the OP. Build numbers will also handle any unforeseen foresight. The users are not consuming the semantic version in any meaningful way they just use the only version of the application. The users will not be sitting on a release or have to rewrite anything because they haven't written anything against a particular version at all. | |
| Jul 15, 2016 at 18:10 | comment | added | Achshar | @RvdK I already have that sorted. I just wanted a way to uniquely identify any particular state of the application and version number is pretty much used for exactly that. So I believe it is a version number question. How the version number is then used is irrelevant. | |
| Jul 15, 2016 at 18:07 | vote | accept | Achshar | ||
| Jul 16, 2016 at 7:56 | |||||
| Jul 15, 2016 at 13:05 | comment | added | RvdK | See: stackoverflow.com/questions/29292051/… | |
| Jul 15, 2016 at 12:58 | comment | added | RvdK | So you requirement is not user related (I want to know which version is hosted), but a software requirement (I want to refresh data). That's unrelated to the build number question. | |
| Jul 15, 2016 at 12:39 | comment | added | Achshar | Your point of not knowing how things will go in future is perfectly valid. But my users are school teachers who log in with user/password and click a bunch of buttons. They don't know and never will know or care about bug fixes, version numbers, etc. But I will heed to your advice of using major.minor. I think I will go with a compromise of major.minor.build. My reason for adding a build at the end is that I need to have a version that constantly changes with even a small change in code. This is needed to invalidate certain important caches on client side. | |
| Jul 15, 2016 at 12:36 | history | edited | David Hammen | CC BY-SA 3.0 |
added 405 characters in body
|
| Jul 15, 2016 at 12:30 | history | edited | David Hammen | CC BY-SA 3.0 |
added 405 characters in body
|
| Jul 15, 2016 at 12:23 | history | answered | David Hammen | CC BY-SA 3.0 |