> From: Rick Winscot [mailto:rick.wins...@gmail.com] > Sent: 23 January 2012 15:32 > Is there anything that prevents us from calling the first build out the door > a 'Release Candidate?' Then in Jira... adding a line item / known issue > logged against it to get automation working?
"Release candidate" implies it's good to ship unless problems are found. "Alpha" is a better choice of name for a release that is missing automation support. How about adopting the odd number = development test releases, even numbers = production releases approach? Whilst working out the release mechanism, patching missing features etc, 4.7.x releases could be pushed out as often as needed. Once a complete and tested version is created, it's rereleased as 4.8 and work starts on 4.9.x releases, which would result in a 4.10 production release etc. David.
