<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">Hi all. A couple of meetings ago I brought this up and promised to start a discussion in the ML.</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">There are two ideas behind this letter:</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">1st) Since we (and openstack at large) started using reno for release notes — launchpad milestones became redundant as a tracking tool of what have been done during development of a certain version of an app.</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">We might still use milestones for what we’re planning to do during a certain period of development, but in my opinion it never really worked, since dozens of open/in-progress bugs get transferred at release time to the next milestone.</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">I’d like to discuss the idea to stop using milestones on l-pad and just target bugs/bps to series.</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">+1 from me on the idea as I don’t see milestones being useful anymore</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br></div>2d) We currently have 3 ways to track something we’d like to implement: wishlist-bug, blueprint, spec. A spec always require a blueprint, but a blueprint doesn’t always require a spec.<div><br></div><div>The idea is to minimise the number of tracking tools we use here and to stop using blueprints altogether. For small features this would mean assigning a wishlist-level bug. And for large features we should file a spec anyway and probably a specially tagged bug.</div><div><br></div><div>Pros: simpler more streamlined release/bug/feature management. One place to search for all functionality.</div><div>Cons: we would have to write Closes-Bug, which is kind of misleading. We wouldn’t be able to track dependencies between bugs the same way we now do for bps.<br><div><br></div><div>I don’t have a strong opinion on this one, so I would love to hear out some opinions on this one.</div><div><br><div class="bloop_sign" id="bloop_sign_1450791720533224960"><div style="font-family:helvetica,arial;font-size:13px">-- <br>Kirill Zaitsev<br>Murano team</div><div style="font-family:helvetica,arial;font-size:13px">Software Engineer</div><div style="font-family:helvetica,arial;font-size:13px">Mirantis, Inc</div></div></div></div></body></html>