This is the jump-start post for the thirteenth week of the WordPress 4.2 release cycle.<\/p>\n
Last week, we missed<\/a> tagging RC1 after losing momentum on our ticketticket<\/span> Created for both bug reports and feature development on the bug tracker.<\/span><\/span><\/span> goals toward the end of the week. We also missed hitting the \u201chard\u201d string freeze.<\/p>\n Committers<\/strong>: please follow up on any tickets you own<\/a>. We\u2019re running out of time to hit our release date goal. We need to freeze strings and actually tagtag<\/span> A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.)<\/span><\/span><\/span> RC1, in that order, as soon as possible<\/p>\n Remaining tickets on Report 6<\/a> that must be closed or punted to tag RC1 are as follows:<\/p>\nCoreCore<\/span> Core is the set of software required to run WordPress. The Core Development Team builds WordPress.<\/span><\/span><\/span> Meetings this week:<\/h4>\n
\n
\n
Priorities this week:<\/h4>\n
\n\n
\nThe recommendation is for @<\/span>wonderboymusic<\/a> to revert [31030]<\/a> and [31033]<\/a> and regroup in 4.3.<\/li>\n
\nWaiting for a followup from @<\/span>westonruter<\/a> on the latest patchpatch<\/span> 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<\/strong>. A patch can be applied<\/em> to a codebase for testing.<\/span><\/span><\/span><\/li>\n
\nLooking for direction from @<\/span>helen<\/a> on what an MVPMinimum Viable Product<\/span> \"A minimum viable product (MVP) is a product with just enough features to satisfy early customers, and to provide feedback for future product development.\" - WikiPedia<\/a><\/span><\/span><\/span> fix would look like<\/li>\n
\nLatest patch needs to be reviewed and committed, and we should decide if the rest is worth tackling in 4.2.<\/li>\n
\nThe recommendation is to commit the latest patch and handle #30725<\/a> following that<\/li>\n
\nThe latest patch from @<\/span>ocean90<\/a> needs to be reviewed and committed by either @<\/span>wonderboymusic<\/a> or @<\/span>jorbin<\/a><\/li>\n
\nThe initial patch needs to be committed so we can keep design separate from content. The About page strings need to be finalized in order to institute \u201chard\u201d string freeze. @<\/span>melchoyce<\/a> and @<\/span>ryelle<\/a> are in the process of engineering and designing around the content<\/li>\n<\/ul>\nRecent notable updates:<\/h4>\n