Application versioning

Posted by Mathew on Programmers See other posts from Programmers or by Mathew
Published on 2014-06-03T19:18:53Z Indexed on 2014/06/03 21:39 UTC
Read the original article Hit count: 206

Filed under:

Haven't find similar issue so sorry if thats a duplicate.

I'm about to start a migration of an already existing project from one web container version to the another. Currently, the application version is 2.2.5. Business requirement is to deliver a 3.0 version by the end of the year. Additional constraint is to release a working, stable version by the end of Q3.

We are about to work in 2-weeks sprints and I'm wondering how can I approach the problem?

I was thinking about releasing 2.3 by the end of Q2, then immediately promoting it as 3.0-a1, work on alphas (3.0-a2, 3.0-a3, ...) till the end of Q3, to start with 3.0-b1 in the early Q4 and finally release 3.0 around December. I don't feel comfortable saying that the application is already in 3.0 state in July, but I can't see other options.

If you find some book chapters/blogs or your personal experience interesting please share your opinion.

© Programmers or respective owner

Related posts about versioning