I'll just post my way of doing this with some minor explanation on why I chose that way. I hope it could be of any help to you. I'll go through my workflow using git on Windows and publishing the code to github.com and wowace.com. I'll also list the tools I use.
The reason:
The main feature I miss on sites like WoWI/WowAce/Curse is the ability to browse addon code online. I like the way things are on github and that's why I did choose git as the VCS to use. I also found the github tutorials easy to follow and it was fast enough for me to achieve what I wanted without any prior knowledge about VCS at all.
The workflow:- Create folder MyAddon in Interface\AddOns
- Code up to an alpha state
- Create a repo on github called MyAddon
- Set up a git repo on wowace called MyAddon
then on the command-line
- cd Path\to\WoW\Interface\AddOns\MyAddon
- git init
- git remote add origin [email protected]:Rainrider/MyAddon.git
- git remote add wowace [email protected]:wow/MyAddon/mainline.git
- git add *
- git commit -m "some witty comment"
- git push -u origin master
- git push wowace master
Wowace/Curse packager will automatically create a downloadable zip for every commit you push. Every untagged commit counts as alpha. Tagged commits are either beta or release based on the tag message. From your MyAddon folder on the command line:
- git tag -a v1.0 -m "Version 1.0"
- git push origin v1.0
- git push wowace v1.0
This will create a release on both github and wowace.
I don't know how exactly things are on WoWI, but as they support git, I suppose the same pretty much applies to it too.
Issue tracking:
I like and use github's as you can close tickets directly from a commit and when you browse the commit there is a link to the ticket it closes and vice versa. On WoWI you could disable file comments and post a link to whatever you want to use. On wowace/curse you can link directly to whatever you want to use (when people click on "Tickets" they get redirected).
A small note:
The name and email you set up with git are publicly available once you push to a public remote as everyone can pull them. Once you tag a beta or a release on wowace, your email and name appear in the change log (for alphas it's just your name). Git does not care whether you enter a valid email address or not and so do github and wowace (again, I have no experience with WoWI). You could set both your name and email globally and per repo where the per repo setting will always precede the global one. Use
on the command line from within the MyAddon folder to set those locally. Remember to set up those in advance if you are uncomfortable with making your real name and email public as wowace won't let you rewrite your repo's history (you could still change the change log manually from the site though, but the commit info is still there)
Tools used:
MSysGit - has a basic GUI and command line support (through the command prompt). It also adds 2 entries to the windows explorer context menu ("Git Bash Here" - opens command prompt at the selected folder, and "Git GUI Here" - opens the GUI). That it what I prefer to use.
GitHub for Windows - sleek GUI (but github.com restricted) and command line (through PowerShell)
Git Guide:
http://git-scm.com/book/