We were scheduled to do RC1 today. With around 100 tickets in Trac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., this is not happening. We did a giant push to meet the beta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. deadline, but then people went back to their other stuff, dealt with 3.1.3 security release along with beta 2, and generally slowed down. I’m pushing back the RC One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). target date on the schedule to Monday.
In the words of Lester Bangs (by way of Cameron Crowe via Almost Famous), let’s be honest and unmerciful in today’s scrub.
- If there’s a patch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing., make the call: is it in or out? If it’s not a blocker A bug which is so severe that it blocks a release. or a regression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. and the patch isn’t quite there, punt Contributors sometimes use the verb "punt" when talking about a ticket. This means it is being pushed out to a future release. This typically occurs for lower priority tickets near the end of the release cycle that don't "make the cut." In this is colloquial usage of the word, it means to delay or equivocate. (It also describes a play in American football where a team essentially passes up on an opportunity, hoping to put themselves in a better position later to try again.) it, even if it is your pet ticket Created for both bug reports and feature development on the bug tracker..
- If there’s not a patch, how bad is the bug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority.? Blocker or regression? Assign it to someone and get a patch for testing by tomorrow. Not? Punt it and hit it early in 3.3.
- We need to fish or cut bait on a number of lingering small UI User interface things. If someone wants to run through them with me we should be able to knock them out today or by tomorrow at latest.
- Licensing tickets. We need to do the right thing in all cases, and we need to do it this release.
- String freeze. I’ll do a run through today/tomorrow and look for anything that we’d planned to update but haven’t yet, including Credits and Freedoms screens. We need to do a check on text in help tabs,too, some still need updating. Will write text change patches myself or have a volunteer do them.
- Any tickets left in the milestone by EOD tomorrow should be blockers.
Let’s get this released tidied up and shipped so we can get started on 3.3!
#3-2, #schedule, #scope