What do people do for revision control? For example, would love to tag a prototype as revision XXX, so it can be handed off to the dev team but I can continue working on the prototype for future iterations.
The need is to lock it down after sign off and have some ability to reference it, all while not preventing me from marching forward. This would also let us say that this revision was signed off on this date. The output is what we want to control, not so much the file since the output is what the business and development team are working off of.
Any elegant solutions to this? I'd rather not create new files each time, that changes the posted URL and it is a big hassle. Best idea I can come up with is to copy the screen so I can work on additional changes. This seems like it can get messy and it isn't structured, depends a lot on individual discipline to maintain. I figure I can add something to the page that says "PROD | QA | DEV" to alternate between the versions. Or we can version control screenshots.
What are other people doing, or are we going about this in an atypical way? Am I missing something basic? We are standing up a complex enterprise web app so this single prototype will have a lifespan of 2-4 years as we mature and iterate the offering.