I know that with shared libraries, it generally is not a good idea to push an update that involves versioning a shared library because the user may have software their system that is linked against the older shared library, but is there a general policy about other software?
One of the packages I maintain in Extras is likely to be named as a sourceforge project of the month. The upstream developer is working overtime to finish implementing some things before that happens. The package is gourmet (PyGTK recipe manager) and absolutely nothing depends upon it - and I'm thinking that when he has these things finished, that might be a good time to update the package in Extras.
Since it is not a package which is designed to have anything else depend on it, I'm assuming there is not a problem with a version update in Extras? Is that the case?
The project is under fairly rapid development but I don't intend to package every little update simply because most of them don't add anything worth an update imho, but I think the update he is planning (after testing) is will be worth pushing an update.