Timeline for Requirement that code changes within release be reverse compatible with DB schema
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 18, 2014 at 2:58 | audit | Suggested edits | |||
| Feb 18, 2014 at 2:58 | |||||
| Feb 16, 2014 at 16:25 | audit | Suggested edits | |||
| Feb 16, 2014 at 22:51 | |||||
| Feb 4, 2014 at 3:42 | answer | added | Karl Bielefeldt | timeline score: 3 | |
| Feb 4, 2014 at 1:06 | comment | added | James Anderson | Sadly forcing your customers into risky, complex and expensive "Big Bang" upgrades is common among large software companies, mostly because they can get away with it. As a small software supplier you risk losing customers if upgrading your product is about the same effort as switching to another product. | |
| Feb 4, 2014 at 0:48 | history | edited | amphibient | CC BY-SA 3.0 |
added 15 characters in body
|
| Feb 4, 2014 at 0:42 | history | asked | amphibient | CC BY-SA 3.0 |