Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Related Rants
Having a question regarding build number semantics (Im working on android app for that matter)
My current app build which is released is 5.3.6 (build number 94)
I already merged one feature to develop but haven't released it.
I also finished working on another feature but haven't merged it to develop yet.
Now my question is should I make a new build (5.4.0 with build number 95) and just merge to master, then release to google play (it would contain both two features)
Or should I make a new build 5.4.0 bn 95, merge to master, release it. And then make another build for the second feature 5.5.0 bn 96 and release that as well?
My reasoning would be to go with 2 separate builds and versions (in case my second feature messes up, I can revert it and also it will be easier to manage versions).
But then what about users: will they receive two updates from google play or only one (the latest version) ?
question