Here's what I've discovered. If I right-click my folder, tortoiseSvn->Commit (Which I assume is the correct way to upload a project), a new alpha file is created named rXX where XX is the version number (eg. r12)
If I right click, go to tortoiseSVN->tag/branch and in the 'to URL' line, change the last directory /trunk/ to /tag/Something, A beta file named 'Something' is created. I do not need to have 'b' or 'beta' anywhere in there.
If I right click, tortoiseSVN->tag/branch and in the 'to URL' line, change the last directory /trunk/ to /tag/Release or /tags/12345 (anything with all numbers), a Release file is created with the name Release or 12345
Does this sound right?
Here's my questions:
How do I make the default commit (the one where I dont have to go to branch/tag or see a URL box where I have to edit it each time) a Beta or Release?
2nd question: How do I bypass the part where I have to put in a message? I dont want to have to type anything, ever, and besides I don't know what I'm supposed to put there, and I keep getting commit failure Because I forgot to type something. I usually just mash the keyboard for a second (adfadf adsf a) and that seems to work.
3rd question: How do I make a release (or beta) that is automatically named vXX (or rXX) where XX is the version number?
I understand I have to edit a pgkfile or something like that, but..... /confused
A version string is the name you give your tags when you do a right click -> tag/branch. If this name contains only dots and digits and optionally starts with the letter v (such as "v1.2.3" or "v1.23" or "3.2") or contains the word "release", then it is considered a release tag and a release zip will be created. If the above conditions don't match, it is considered a beta tag and a beta zip will be created.
All other commits (that are not tags) are alphas and alpha zips will be created.
1) You cannot make commits beta/release by default. The whole point of SVN is to be able to control your source code, and using SVN to see the code differences between each version. When you make a commit, in the bottom half of the commit box, you will see a list of files that has changed since your last commit. Go double click on one of those files. You will open a "diff" which shows you a list of source code changes line by line.
2) You must put in a message describing the changes you are committing. Try to make this descriptive so that 6 months later when you are reveiwing your code, you can figure out why you made the changes you did. (You can see past changes by using the View Log option in the SVN right click menu)
3) You just tag it as outlined above with the naming you want. Generally speaking, you normally will not want your addon's version numbering to be the same as SVN's numbering which just increases by 1 every commit.
A) The URLs for you would be different since its a different project
B) When you first checkout from the server, you will get an empty folder since it is a new repository. After you checkout the empty folder (so called version or revision 1 of your addon), move your addon files back into the folder and perform the commit that uploads your changes (from an empty folder to one full of your addon files) to version or revision 2.
C) You may get an error about setting eol-style:native. If you do, right click on your files you wish to commit, look at the tortoisesvn properties (in the tortoisesvn menu), and add a new property called eol-style (choose this from the dropdown menu), and just type the word "native" in the box (without the quotes). This topic about eol-style is covered in one of the later posts in the thread linked above as well.