give additional use case for version bumping; remove no longer true statement about version strings

Originally committed as revision 14470 to svn://svn.ffmpeg.org/ffmpeg/trunk

1 files changed, 3 insertions, 2 deletions

diff --git a/doc/general.texi b/doc/general.texi
index ea252e85c5..a0a888129d 100644
--- a/doc/general.texi
+++ b/doc/general.texi
@@ -898,11 +898,12 @@ should also be avoided if they don't make the code easier to understand.
 @item
     Remember to check if you need to bump versions for the specific libav
     parts (libavutil, libavcodec, libavformat) you are changing. You need
-    to change the version integer and the version string.
+    to change the version integer.
     Incrementing the first component means no backward compatibility to
     previous versions (e.g. removal of a function from the public API).
     Incrementing the second component means backward compatible change
-    (e.g. addition of a function to the public API).
+    (e.g. addition of a function to the public API or extension of an
+    existing data structure).
     Incrementing the third component means a noteworthy binary compatible
     change (e.g. encoder bug fix that matters for the decoder).
 @item