<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Jul 18, 2010, at 1:46 PM, Alexander Belopolsky wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Menlo; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="font-family: monospace; ">We already have "posponed" and "remind" resolutions, but these are<br>exclusive of "accepted". I think there should be a clear way to mark<br>the issue "accepted and would be applied if X.Y was out already."<br>Chances are one of the resolution labels already has such meaning, but<br>in this case it should be more prominently documented as such.<br></span></span></blockquote></div><br><div>This is what branches are for.</div><div><br></div><div>When the X.Y release cycle starts, there should be a branch for X.Y. Any "would be applied" patches can simply be applied to trunk without interrupting anything; the X.Y release branch can be merged back into trunk as necessary.</div><div><br></div></body></html>