I missed this blog post recently, in the heat of the recent Australian federal election. But it’s another very interesting article into the world of the core developers. Wilco provided the Joomla! user community with a very concise overview of what it means to progress from one Release Candidate to the next. Unfortunatley there was no hint of a possible timeline, but it’s exciting reading nontheless. Here’s a snippet from the post:
- The main purpose of the Release Candidate is to improve stability. Each new release must strive to be more stable than the previous one. Issues that arise from patches to seriously flaws or security issues that counter this but we work on minimizing this so these will be exceptional circumstances.
- Goals are to be set so that we can measure performance, and be accountable to each other and the community. Stable should be declared when all priority 1 (P1) and 2 (P2) artifacts are resolved and all translations have been completed.
- Every week (or bi-weekly) we review the Tracker with the team to discuss if the trunk is ready for either Stable or the next Release Candidate. Goals for the following week(s) should be set (for example, to resolve all P2 artifacts) based on the resources available. The number of each artifact type, including a break-up of new and existing artifacts, should be recorded at each meeting to be able to measure progress.
- The release cycles are set by these meetings and there is no limit to the Release Candidates subject to the prior conditions being met (that stability is improving, etc), nor is there a set time frame. If a Release Candidate can go out every week or every four weeks as long as stability is improving.
Be sure to read the full post at the official Joomla site.
…I can’t help myself, the election is over, and it’s a new period for Australia. Thank you to everyone who voted to kick out Howard!
Filed under: Uncategorized
