Time to publish new view

I'm currently working with our SOE and as part of it we are deploying a custom rpm as a Product.
So the iterations of the rpm are frequent.
And as I'm typing I'm coming up with a solution, but if I up the release version of the rpm, and add it to the repo I have to publish a new content view to incorporate it in a new build.
So the solution is to not reversion the rpm - simply delete the old and upload the revised but not reversioned rpm and that's probably OK, but my original question remains - and that is whether there is a method for adding a new version rpm to a published view or whether that breaks the logic.
Publishing a new version content view takes a fair bit of time.