I meant to use something like releasing every build we make as a "beta" release (i.e. before a final mayo version).
I consulted this with the pillow yesterday <!-- s:P --><img src="{SMILIES_PATH}/orc4.gif" alt=":P" title="Razz" /><!-- s:P --> (it's a very wise pillow, you know? <!-- s:lol: --><img src="{SMILIES_PATH}/orclaught2.gif" alt=":lol:" title="Laughing" /><!-- s:lol: --> ) and it came to me that we have had problems building the latest public betas "ourselves" because most of the sprites, maps, etc. in our data files are "compiled" apart from the code and the most needed data files are built automatically on our source code compiling process, so why not build everything in a single step? it would make things easier for us as developers, we would only add the new relevant sprites, maps, text files for conversations, you name it, to the SVN repository and hit the compile.bat process and TADA! everything is built for a normal release (including the compilation of PK3 files with sprites, maps, text files, etc.), it would also save us the problem of having to upload beta versions, anyone interested on testing would access to the SVN repository anonymously and download everything from there, run the compile.bat file and play the latest revision of our project, they wouldn't have write access, since their access is anonymous (I'm not sure if we allow anonymous access there, but I'll check it out <!-- s:) --><img src="{SMILIES_PATH}/orc2.gif" alt=":)" title="Smile" /><!-- s:) -->).
I'll be working on making this a possibility on the next days, it will definitely be a more dynamic process for development and make it easier to fix stuff. I'll also be posting details on how to build all this for developers and users alike in the Wiki, I'll post a link here to the article and in the new forums for public development ASAP.
I'll begin this work with KRPG, and follow with KA later.