Yes, I suppose that would work, but it would take up lots of server space and might be confusing if there were too many different releases.
Would take up very little server space, we're talking about source code here... and the SVN isn't really meant for everyone, developers are likely to know what's going on in each branch.
One way would be to make everything "stable" before incorporating it into GAE. Another option would be to provide patch files that people could choose to add or not. However, this would mean that lots of people would have slightly different types of glest, and so to play a new mod, you might have to recompile glest. I think the easiest thing to do would to get every new piece of code stable before adding it to GAE.
As an end user, all you really need to worry about is the trunk 'stable' release. Unless you want to help testing new features... for which you will indeed need to be able to compile. All these other branches is simply
how (or perhaps, 'where') we get things stable before moving them into the trunk.
Apologies to titi for the unintentional hijacking of this thread.
To go back OT, Great job compiling this titi, and to everyone involved in the mods.
And I'll throw my hat in for 'incremental' updates too, it is getting big...
Edit: Apologies to titi again, I didn't realise this was
all your work, incredible job!