release version scheme

[olumolu]

X.Y.Z
Lets say the variable x can be chnaged for major upgrade or chnages in the app such as a 35-<.. commits.
Y variable for 15-25
For Z 3-15

don't use terms such as small update various fix many fixes and some feature update.

This thing can be in the description rather just add the version number that is all.

[Jeffser]

yeah maybe but I do like the funny release titles like 'another small update', I think it makes the app development more personal

[olumolu]

Change release cycle and design
Ad whenever you want to publish a new version obviously there are some update for translation and stuff sometime none but
I would recommend to initiate discussion and ask translators for update so it can be done and publish a full fledged translated app. As it was but due to your release translator don't know the update of .pot so they can't update them.
As you update pot and publish with in a 30min span.

[Jeffser]

I don't want to bother translators asking them to translate the app before the newer version comes out, I also don't want to wait for every translation to get done before releasing a new version. Everyone has their own schedules and I don't expect my app to have up to date translations all the time

[olumolu]

Understand your point.