Timeline for How to keep user's guide in lockstep with branches for a non-developer?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 1, 2012 at 23:58 | history | notice removed | yannis | ||
| May 1, 2012 at 23:56 | history | notice added | yannis | Needs citation | |
| Mar 15, 2012 at 7:27 | comment | added | Doc Brown | @sarumont: if a few commands on a sticky note are not enough, there seem to be a problem which has nothing to do with version control. Those problems you will also face if you would not use version control to hand the docs over (for example, by mail or by using a shared server folder). | |
| Mar 14, 2012 at 19:24 | comment | added | jcmeloni | @sarumont Perhaps so, but really, I've had even the most non-technical person be able to follow along eventually...no need to mess up everyone else's workflow (or the product) because one person can't. Good luck! | |
| Mar 14, 2012 at 19:21 | comment | added | sarumont | I'll probably give #1 a go this time around to see how it works. I have a feeling, though, that her environment may be a bit convoluted (requiring more than a few commands on a sticky note). | |
| Mar 14, 2012 at 18:56 | history | edited | jcmeloni | CC BY-SA 3.0 |
added 42 characters in body
|
| Mar 14, 2012 at 18:38 | history | answered | jcmeloni | CC BY-SA 3.0 |