Updating versionCode to 9351 and versionName to 0.9.35-1 for 16kb release on Andorid

[automaton82]

Bumping play store version for 16kb release.

@perepujal please check if I did the version correctly.

[perepujal]

Correct :)

I usually keep -0- endings for the official Tux Paint version, like 9350 for 0.9.35
1-5 endings for updates on the same Tux Paint version that are meant to be released to users,like your current update or bugfixes in the past.
-6- endings for developement, not meant to be released outside of developers.
7-9 endings for pre-releases of the next Tux Paint version meant to be released to betatesters, When Tux Paint 0.9.36-RC1 will be released, the APK should be 9357, 0.9.36-RC2 goes to 9358 and so on.

Up to now this schema has worked, we have 5 namespaces for corrections/updates and 3 namespaces for pre-releases.
If some day we run short of numbers, then we will need to rethink this schema...

[automaton82]

Correct :)

I usually keep -0- endings for the official Tux Paint version, like 9350 for 0.9.35 1-5 endings for updates on the same Tux Paint version that are meant to be released to users,like your current update or bugfixes in the past. -6- endings for developement, not meant to be released outside of developers. 7-9 endings for pre-releases of the next Tux Paint version meant to be released to betatesters, When Tux Paint 0.9.36-RC1 will be released, the APK should be 9357, 0.9.36-RC2 goes to 9358 and so on.

Up to now this schema has worked, we have 5 namespaces for corrections/updates and 3 namespaces for pre-releases. If some day we run short of numbers, then we will need to rethink this schema...

Sounds good, thank you!