So I start writing a script - in npp - and then a bug pops up and I start adding debugging code. Or I decide to change the general approach. How do you rename your scripts in the hard drive in such cases - so you can see the main development "trunk" and the "branches" growing out of it ? Does any of you have a general approach/ naming convention for this ?

Thanks

The software industry uses a concept called http://en.wikipedia.org/wiki/Revision_control to do this.
Last year there was a discussion on the forums about how to apply it to scripting, but I did not follow it that close.

I, myself, don't do much more than, on occasion, creating a copy of a script and append the name with "OK" or "Backup".
What I do most often (every few hours to every few days), for backup purposes, is making a copy of the wip esp in the Data folder and, also, copying the original and the copy to a backup folder in a different drive.

I knew I'd seen "trunk" and "branches" someplace
Yes this is what I meant - but sacaled down
Thanks for tips

Source Control systems are more for multiple developers working on the same code. If there's only one, then copying the scripts to text files as backups from time to time would be enough. Just cut-and-paste the whole thing into notepad or equivalent and save a copy in another folder.

It's useful to do that for commonly used code snippets that you'll reuse in other scripts - things like the "wait three days" logic that you'll use again and again. It's easier to paste them in from a library of useful code parts then type them from scratch every time.

Thanks
I am mostly writing my scripts in notepad++ and only compile them in the CS - so my question is about a naming convention for naming them while working on them like
scn00.es4
scn01(debug bug foo).es4
scn011(debug bug foo and bar).es4
this doesn't seem to work
maybe someone has a convention would like to share - I don't think there is an IDE for ob scripts lol