Patterns and conventions to document changes while developing
Posted
by
Talysson
on Programmers
See other posts from Programmers
or by Talysson
Published on 2014-06-06T14:37:55Z
Indexed on
2014/06/06
15:40 UTC
Read the original article
Hit count: 129
documentation
Let's say I'm developing a second version of an API, and there's some changes in method names and so on from the previous version.
What's a good way to document these changes ? I mean, is it better to document while changing (but, maybe, there will be more changes before the release, so I think it could be more work than necessary) or write down some topic and document after all the changes are done ?
© Programmers or respective owner