I've redirected all existing pull requests from master to the develop branch.

As for the suffix that's only needed if we do two releases in one day right? Well if we ever need it then yes we could YYYY.MM.DD.PATCH, but I usually simply YYYY.MM.DD+1 to keep the format consistent

Just wondering, does travis provide a way to upload build artifacts somewhere? It would be nice if we could test the APKs built automatically, even if that testing is not itself automatic yet.

Yes it does but I've never played with it

By the way, now I'm thinking how do we want to handle the .. versionchanged:: parts? It probably means on develop this string will be incomplete because we don't know the version upfront. Then we can review/fill these incomplete strings while preparing the release branch

Maybe we should change from master to develop this line:

def modified_recipes(branch='origin/master'):

At: https://github.com/kivy/python-for-android/blob/develop/ci/rebuild_updated_recipes.py#L34

I'm thinking that on the develop branch we should use version YYYY.MM.DD.1.dev0, where the YYYY.MM.DD comes from the latest release version. That should mean that pip orders the version correctly. We would expect that the next release would not actually be YYYY.MM.DD.1, it's just a convenient way to mark correctly that the develop branch is newer than the master branch. Any objections to taht?

That makes total sense 👍

Thanks @opacam, fixed that reference.
As far as I'm concerned this is good to go, I'll merge it as soon as someone approves it again.