I'm looking for a Software Release Cycle Map (similar to the one at Wikipedia), but for Joomla!
I am specifically not looking for projected release dates or length of support as part of this answer
I'd like to confirm (or if I'm incorrect, get the following information down accurately, including the terminology used by the Project Leadership Team).
- Release Candidate (RC)
- Release to Marketing (RTM)
- General Availability (GA)
The reason is that I would like to test my clients' sites (which are packed with extensions from various providers)against the Beta.
I can set up another development server, clone the live site (password protect the directories) and upgrade the Joomla! core to the Beta.
I need some instructions as to the correct way to configure the cloned test site to update to a specific Beta release.
There are drop-downs in the Joomla! Update Configuration (J!2.3.2) which don't seem to align, or do not provide the level description so that I know which version I'm updating to (i.e. what is 'testing'?) in the context of the above.
There is an option to enter a 'Custom URL' - but I'm not sure this lets users upgrade to test Beta.
I am a little lost with how to assist with testing at the Beta stage, but I believe this would be of value to both the Joomla! CMS, the extension providers and of course site owners because it would provide an opportunity to test a cloned live site early in the release stage and to report and work out any bugs early on.
Of course, the test would continue through the various Betas, to RC etc., so I would need to know how to set the Joomla! Update Configuration to update to the specific version of Joomla being tested.
Also, because I am little inexperienced, so if I am heading down the wrong the road, please feel free to clarify and suggest a better approach.
The end-goal should be to be able to test early and continuously through the Beta and RC phases, provide feedback on any bugs to the Joomla! Project Leadership and Extension Developers, and then have a smooth transition to go live with the update CMS's for clients (in other words, I'm trying to figure out how to catch and communicate potential bugs early in the game).