The keywords fixed major and fixed…

The keywords “fixed-major” and “fixed-minor” can be used for tickets that span both a minor and major milestone. A ticketticket Created for both bug reports and feature development on the bug tracker. fixed in the major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope. (and then usually re-opened for minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. consideration) will not show in reports 5 and 6. A ticket fixed in the minor release (and then usually needs more work for a major release) will not show in reports 3 and 4.

The ticket does need to remain open and set to the minor release milestone, so really it’s just a way for committers get it out of sight, out of mind when appropriate. Eventually a ticket tagged fixed-major will either be backported or not (and closed either way), and a ticket tagged fixed-minor should either be dealt with in a timely fashion, or split into two tickets.

#keywords, #trac