He wants the ability to package head, and to put that in the updater. So adding a new level would just mean the updater could also grab that level, and we'd be back where we started. The advantage with adding a "dev" tag for commits is we'd then have two "test" tags to utilize. But add-ons probably don't need that much granularity -- it's either "very raw, you probably shouldn't touch -- alpha", "buggy but testable -- beta", or "release quality".

hmm.. I still think there should be a wip category, which would be do not touch unless you are coding, but then that is probably because I am one of those that works on different machines and would like to have place out of the net to start the files when it is time to go to eat etc and I will likely be in a different place when I pick work back up again.

That's really what you should be using temporary branches for. But I did notice this earlier today....

[www] curseforge-packager: ckknight * r255 / (2 files in 1 directory): If a tag ends with -alpha, treat it like a beta, except mark it as alpha on upload.

Which I'm guessing is a way of getting alphas packaged while having normal alpha packaging disabled.

That is exactly why we added it. For the people who want to be able to develop in trunk without fear of people downloading it or it showing up in the client. Just disable alpha packaging and then you can tag as an alpha when you're ready.

That is exactly why we added it. For the people who want to be able to develop in trunk without fear of people downloading it or it showing up in the client. Just disable alpha packaging and then you can tag as an alpha when you're ready.

1. only allow release on curse. this will force authors to release if they want their addon on curse.
2. allow curse client to select beta, if user chooses.
3. allow authors to restrict alpha access on wowace. maybe have a test group in addition to authors for each project.

i agree 99%
just replace 'curse' with 'wowinterface'. that could be so nice. :p