Timeline for How do you maintain a common library used by different clients?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 23, 2012 at 9:02 | vote | accept | Louis Rhys | ||
| Aug 23, 2012 at 9:01 | vote | accept | Louis Rhys | ||
| Aug 23, 2012 at 9:01 | |||||
| Dec 1, 2011 at 23:36 | history | edited | Thanos Papathanasiou | CC BY-SA 3.0 |
added 383 characters in body
|
| Dec 1, 2011 at 23:06 | comment | added | Thanos Papathanasiou | semantic versioning should be more recognized as a best practice! I was about to add it in my answer but I left it out for some reason :/ | |
| Dec 1, 2011 at 23:00 | comment | added | Kim Burgess | See How to design a good API and why it matters. Also, be strict with your API versions. See Semantic Versioning. | |
| Dec 1, 2011 at 22:08 | comment | added | Thanos Papathanasiou | @LouisRhys I added the Wikipedia article though its not much. Basically you get to define the accessible (from the consumer) methods/classes formally. What are the inputs expected and what are the outputs/exceptions. | |
| Dec 1, 2011 at 22:04 | comment | added | Louis Rhys | what do you mean create a public API? . | |
| Dec 1, 2011 at 22:01 | history | answered | Thanos Papathanasiou | CC BY-SA 3.0 |