Server and client versioning

[hasan7n]

From the team discussion today:

• The current central server code is outdated. Adapting the existing database with the recent changes might take a while to work on. We will deploy the new server with a fresh database, and keep the current one aside for later migration.
• We want to ensure that most server-related open issues will be resolved soon before we deploy the new server version.
• After deploying the new version, we should make sure database migration happens through Django migrations unless there are some changes that require users' consent/choice (we will discuss later what defines "changes requiring users' consent").
• We will start the "versioning workflow" (designed/specified by @johnugeorge ) in the next two weeks, hopefully. We will start with version 0.X for now.
• Before starting with versioning, server-related PRs can be merged although the client will not be compatible with the currently deployed server.
• Once the new server is deployed, the database will be empty. We should keep in mind that before having a "public interface" for any user to interact with the central server, we should migrate (manually) the databases to the empty database.

@msheller @aristizabal95 @johnugeorge please add anything I missed

[hasan7n]

outdated