I've already decided that 2 separate DLS servers would be the best route - that way we could retain full service for those who want to stay with the old versions, and those who want to move forward. The improvements that older versions
require will never come (where was SP2 for 2006?), so freeze the DLS development for those versions and move the 2.9+ content to it's own server.
In regards to uploads, please keep in mind that TRS2004/TRS2006 covers 7 versions alone (version numbers in configs that is): 2.0, 2.1, 2.2, 2.3, 2.4, 2.5, 2.6
Correct me if I'm wrong, but one of the ways that this could be worked around would be to require users to patch up to a specific build? AFAIK, it was Sp4 for 2004 and Sp1 for 2006. Personally, I can't see any reason for not patching up to the latest SP anyways, but I'm not really a route builder/content creator.
As there are editions of TRS2004 and TRS2006 that did not receive patches (for what ever reasons), we would need to provide upload support for all of these versions. This actually means that we need to cover 7 different config.txt variations alone (since each build can add and remove tags depending on updates that may be made).
Once again, this could be solved by only allowing access to fully patched versions. If Auran didn't supply certain publishers with patches, that's their fault, not ours.
Plus the following builds, which will be supported after September: 2.7, 2.8, 2.9, 3.0, 3.1. Thats 12 builds so far, each with it's own changes to available tags for the config.txt files, not including the multiple different 'kinds' of assets. This does make the automatic checks for the uploads system very clunky, and much more than it should be.
How is this so difficult to deal with? Asset checking should already be don against a list of valid tags for each build number. As the earlier builds, like I said above, aren't going to recieve any more service packs, it would make sense to assume that the available tags for each of those builds could be considered set in stone.
----
I don't like the idea of having to mess about with FTP links or using the DLS web-page to get every missing dependency, but since I use 2006 the most I have become used to hitting the Web-DLS when CMP fails to find a dependency that is known to be on the DLS.