Versioning releases like a pro

March 2018 by Gabby Littler / Senior Mobile Developer

Versioning releases like a pro

We all know that a project should have a version number. When you release new features, you should increment your version number, right? But exactly when in the development process is that? And how do you keep track? This article describes the simple strategy that I use across our mobile app projects at Control F1.

Although I’m writing about mobile apps, the principles apply to any software development project. So please read on, even if you’re not part of the mobile revolution.

Aims of versioning

Before getting to the when and how, let’s start with why. My main aims are that:

  • Everyone should know what features are available in the version of the app they have
  • Everyone should know what version of the app they have if they are reporting bugs or requesting support

When I say everyone, I mean anyone who uses your app, including internal testers, beta testers and end users.

Please click here to read the rest of the article

Sound interesting?

If you've got a project and it sounds like we might be able to help you please drop us a line.

Let’s talk

We’d love to get to know you and your business a bit better.

You can call us on +44 (0) 845 075 3586, or drop us a line to: hello@controlf1.co.uk.

 Security code
Please enter the text from the image