I'm the product manager for two of my company's application sets, and I've been running into some difficulties trying to manage future releases and how best to move them around. If I have version 2.2 currently in development, I have versions 2.3-2.5 already plotted out in Bugzilla. However, we are now planning on bumping a few items from 2.2 and adding a couple of other small items to make a quick release which will be called 2.3.
If I keep following my current system, I will need to update all 2.5 tasks to 2.6, 2.4 to 2.5, and 2.3 to 2.4.
I've thought about doing something like Future.10, Future.20, Future.30 - this would allow me to add in Future.15 or anything else in between. I feel like this is a problem that has been solved already, but I just don't know how. Is there a better, more generic way to plan out release order that won't require me to adjust every single future release if we add a release in or move things around?
For clarification: This question is purely about pre-development organization of several groups of features ("a release") and the best way to reorder releases without changing all tasks each time I change around the intended order.