psycopg2-cffi should have the same version number of psycopg-c to show the user what feature set it implements. So If you merge #10 I suggest you to bump version to 2.5
If bugs are found in -cffi and a new release is necessary before psycopg2-c you can use the ".post" part suggested by PEP 386: 2.5.post1, 2.5.post2 etc.
After the psycopg2 release 2.5.1 you would have psycopg2-cffi 2.5.1 too. If you find a bug you would release 2.5.1.post1, 2.5.1.post2 etc.
Hello,
psycopg2-cffi should have the same version number of psycopg-c to show the user what feature set it implements. So If you merge #10 I suggest you to bump version to 2.5
If bugs are found in -cffi and a new release is necessary before psycopg2-c you can use the ".post" part suggested by PEP 386: 2.5.post1, 2.5.post2 etc.
After the psycopg2 release 2.5.1 you would have psycopg2-cffi 2.5.1 too. If you find a bug you would release 2.5.1.post1, 2.5.1.post2 etc.