🚀 go-pugleaf

I like to start version numbers of files that users are going to see often, like scripts that require them to drop files onto or they keep on their desktop. Just for sanity sake, i release a 1.0 version then tell people to update sometimes to "1.2" or whatever I deem the next useful version.
I have scripts for users that stay in their ID scripts folder, and a master updater script that they can run to load the latest version to their local HD, so none of those files have V numbers since they can all change often. I also need to have long names to describe thier functions and the 4 extra characters i need to have sometimes.
One last bit, i have gotten in the habit of putting the build date or an internal version number in the comments at the beginning of a script when I make changes so i can see internally what the last change was even if the file name doesnt have a number.

Chris