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 | |
|---|---|---|---|---|---|
| Sep 27, 2017 at 0:01 | comment | added | Criticizing Israel not allowed | Just use the git commit ID then? | |
| Jul 20, 2016 at 8:35 | history | tweeted | twitter.com/StackProgrammer/status/755682424588275712 | ||
| Jul 15, 2016 at 20:57 | answer | added | pllee | timeline score: 2 | |
| Jul 15, 2016 at 18:07 | vote | accept | Achshar | ||
| Jul 16, 2016 at 7:56 | |||||
| Jul 15, 2016 at 12:45 | review | Close votes | |||
| Jul 20, 2016 at 3:04 | |||||
| Jul 15, 2016 at 12:31 | comment | added | Achshar | I need version numbers to invalidate browser caches on client side. | |
| Jul 15, 2016 at 12:23 | answer | added | David Hammen | timeline score: 2 | |
| Jul 15, 2016 at 12:23 | comment | added | David Arno | Why have a version number at all? If you are serving a web app and everyone is using the same version, there what point would the version or build number serve? I'd have thought you'd be better off simply tagging git (or whatever source control you are using) with eg, the date and time, prior to each update. | |
| Jul 15, 2016 at 12:20 | history | edited | Achshar | CC BY-SA 3.0 |
edited title
|
| Jul 15, 2016 at 11:35 | history | asked | Achshar | CC BY-SA 3.0 |