Set version to 0.5.4.

[mlt] / docs / policies.txt

diff --git a/docs/policies.txt b/docs/policies.txt
index 5aad1d19d4ecd1880fb807b81a5ae0d06671cf7f..60ba1db5ac78d384e65ae8b282f50fdc2616026c 100644 (file)
--- a/docs/policies.txt
+++ b/docs/policies.txt
@@ -22,9 +22,9 @@ Commit messages must be prefaced with the name of the changed files. This makes
 the Subversion log more useful as a ChangeLog. For example,
     docs/policies.txt: added policy about commit message
 
-Increment the version number in ./configure AND mlt.h on the first commit after
-a release as well as just prior to a new release. This way we can track if
-someone is using an unreleased version from the source code repository.
+Increment the version number in ./configure, mlt.h, and melt.1 on the first
+commit after a release as well as just prior to a new release. This way we can
+track if someone is using an unreleased version from the source code repository.
 
 Do not write messages to stdout. stdout is reserved for writing streams that
 can be redirected: e.g. raw DV in consumer_libdv. I recommended to use the
@@ -50,6 +50,13 @@ copyright the MLT integration code as your own. However, if you have heavily
 modified the original code beyond nearly all recognition, you can copyright it
 as your own and attribute the original author as inspiration.
 
+A producer should validate its input and return NULL on failure.
+
+A filter or transition should express the image format it wants before calling
+mlt_frame_get_image(). It should expect to receive what it requested as long
+as it is yuv422, rgb24, or rgb24a and you are using the imageconvert filter
+(typically via the loader producer and its loader.ini file).
+
 Bug Reporting:
 First preference is to use the SourceForge tracker:
 http://sourceforge.net/tracker/?group_id=96039&atid=613414