Changing this requires changing the import path of the generated R file, which
will unnecessarily affect most of the code. R is built in a package based on
the AndroidManifest.xml package name, whereas the final app package name is
overridden in app/build.gradle for free and donate versions.

Untested, we need to find x86 and MIPS devices to test with.

maven-push.gradle source:
https://github.com/chrisbanes/gradle-mvn-push

Talked with zzz and did more research, the overhead of Enum is minimal compared
to the benefits it provides.

Enums often require more than twice as much memory as static constants, and
should be strictly avoided on Android.
https://developer.android.com/training/articles/memory.html#Overhead

The advantage of this change is that client library users can directly compare
the status values they get from IRouterState to the constants, instead of
parsing a string representation of an Enum.

If we move to increment-by-one instead of calculating the version code, we need
to keep the code above the current highest generated code, so that F-Droid will
order new builds correctly above old builds.

If we decide to go back to calculating version codes later, it is possible - we
can increment the version code 2047 times before it will clash with the one for
0.9.14.

https://github.com/WhisperSystems/gradle-witness

now on Java 6 (API 9).