version control - What Is The Proper Location For One-Offs In VCS Repos? -

I have recently started using mercurials as our VCS. In the past few years, I have been RCS, CVS, and - for the last 5 years - SVN.

13 years ago, when I used CVS and RCS primarily, large projects were edited in place on CVS and one-off specific server and were stored in RCS. It worked well because one-offs were usually specific to the server and the server was supported overnight.

Go ahead for more than a decade and many one-off scripts have become less centralized - they may be required at some random time on any server. It was also okay, because now I was an appetizer SVN user. Everything (except the docs) was thrown in a repo

Jump on 2010. Now I am using mercurials and re-putting big projects in my own repo. But what to do with one-off?

Option as soon as I see them:

• A repo for each script.
It seems that to create a repo for every single page script, it may seem a bit rusty, which can be run once a year.
• RCS
Not an option. There are many potential servers for which specific scripts may be required.
• Use SVN to continue for only one measure.
No. I do not see any advantage over the next option.
• Make a reparse by the name "one-off" named Mercurial.
This seems most practical

The last option seems best to me - though; Is there a best practice about this?

You may also think that these scripts are actually one-off if they will be reused. Some of them can be reused for 6 months or one year from now - nothing, never. However, almost all of these include many man-hours work due to complex logic or extensive error checking. Just do not have the skill to leave them.

I agree with your analysis. In fact, if you do not want to leave something, then you can deposit it from somewhere: -) <4 p>

The last of the proposed options is definitely the most understandable.

In addition, you can store scripts in your CMS (if you have one, and if it is strong enough for your taste). Depends on whether it is more convenient / manageable.