Create Server Release

[lfield]

The server requires a separate document as the processes is different from the client. For example binary build products are not required on Windows, Mac, Linux and Android and the Alpha testers project may not be used in the same way. There is a great deal of overlap (this is a copy and paste) so we may wish to combine in some way to meet the DRY principle.

[TheAspens]

I agree about the overlap and DRY. I need to make some updates to the client release process (specifically making some diagrams of the branch merge strategy and splitting that into a separate document). I will also need to update the development workflow to reference the branch/merge strategy. Once I do that it might simplify what needs to remain to define a "client release" vs "server release".

[drshawnkwang]

Two minor comments:

1. Please 'convert' this document to markdown (.md), so that GitHub displays it in a more readable format by default.
2. I am not a big fan of the even/odd numbering scheme for testing and stable releases. But this isn't something I feel very strongly about and am willing to see how it works.