-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 bugs buggy wrote: > Anyone have any opinions on what should be done? Another option: How about adding version checking stuff to 2.1.3 and then releasing 2.1.3 + some non-netcode fixes? When releasing 2.1.3 add information on our plans for 2.1.4 (see below) to the release announcement, so people are prepared. Not sure how version checking is achieved, but I hope that it is possible to implement version checking without breaking backwards-compatibility to 2.1.2. Perhaps some behaviour of versions prior to 2.1.3 could be used as an indicator.
Then in 2.1.4 you could add that networking fix as 2.1.3 users have version checking and one should assume that most people upgraded to 2.1.3 in the meantime. More stable netplay would surely convince most people to use 2.1.4 anyway. - --> 2.1.4 will not work with 2.1.3 or any other version prior to 2.1.4. But that should be okay as the advantages people get in exchange for incompatibility should outweigh the disadvantages. More stable netplay was _the_ main goal for 2.1, so that sacrifice is justified. Eventually people will understand that. Yet another option (just to have mentioned that one as well) is to not use the fix for netplay (aka the unfixed netcode), if 2.1.3 or no version is detected. Dirty: Yes. Convenient for the users: Yes. Convenient for distributors: Yes. Going to a stable 2.2 ASAP could help with overcoming this "mess". P.S.: Everything's IMHO ;) - - Kreuvf -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJu3im4y86f1GXLDwRAih7AJ9ovG9wI02t69WNMzgR3A4P8kMQnQCfRJBG 3vM7pOV5klowA0hQzzSWP5E= =G7Ik -----END PGP SIGNATURE----- _______________________________________________ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
