<div dir="ltr">Great, thanks!<div><br></div><div>I'll assume unless someone speak up with a -1 or other objection that this is the plan moving forward.</div><div><br></div><div>Cheers,</div><div><br></div><div>Nick</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr">On Fri, Sep 14, 2018 at 2:21 AM Lars Heinemann <<a href="mailto:lheinema@redhat.com">lheinema@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="text-align:left;direction:ltr"><div>Sounds good to me.</div><div><br></div><div>Lars</div><div><br></div><div><br></div><div>-------- Weitergeleitete Nachricht --------</div><div><b>Von</b>: Nick Boldt <<a href="mailto:Nick%20Boldt%20%3cnboldt@redhat.com%3e" target="_blank">nboldt@redhat.com</a>></div><div><b>An</b>: <a href="mailto:jbosstools-dev@lists.jboss.org" target="_blank">jbosstools-dev@lists.jboss.org</a> <<a href="mailto:%22jbosstools-dev@lists.jboss.org%22%20%3cjbosstools-dev@lists.jboss.org%3e" target="_blank">jbosstools-dev@lists.jboss.org</a>>, devtools-devsuite <<a href="mailto:devtools-devsuite%20%3cdevtools-devsuite@redhat.com%3e" target="_blank">devtools-devsuite@redhat.com</a>></div><div><b>Betreff</b>: [jbosstools-dev] Proposed new approach to devstudio milestones when blockers/criticals are found: ship with Known Issues</div><div><b>Datum</b>: Thu, 13 Sep 2018 15:48:02 -0400</div><div><br></div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr">A couple days ago, the Fuse Tooling team encountered what was at first thought as a blocker, but later downgraded [0].<div><br></div><div>This brought up the issue of what to do when problems are found late in the QE test cycle (3hrs before the usual signoff). </div><div><br></div><div>There are of course 3 options when this happens:</div><div><br></div><div>a) block the release and <b>respin</b>, then wait 4-6 hrs for new bits, and some number of hours for QE to review & approve the changed build. Release ends up being delayed by a day or two</div><div><br></div><div>b) block the release and <b>DO NOT SHIP</b></div><div><br></div><div>c) release <b>AS IS</b> with note about Known Issues on the project's New & Noteworthy [1] page and on the blog [2].</div><div><br></div><div>[0] <a href="https://issues.jboss.org/browse/FUSETOOLS-2799" target="_blank">https://issues.jboss.org/browse/FUSETOOLS-2799</a></div><div>[1] <a href="http://tools.jboss.org/documentation/whatsnew/jbosstools/4.9.0.AM3.html#fusetools" target="_blank">http://tools.jboss.org/documentation/whatsnew/jbosstools/4.9.0.AM3.html#fusetools</a></div><div>[2] <a href="http://tools.jboss.org/blog/4.9.0.am3.html#fuse-tooling" target="_blank">http://tools.jboss.org/blog/4.9.0.am3.html#fuse-tooling</a></div><div><br></div><div>Along with the new approach to doing fewer milestone releases [3], I'd like to propose that we:</div><div><br></div><div>* stop doing respins UNLESS it's a GA candidate build. </div><div><br></div><div>[3] <a href="https://docs.google.com/document/d/1zmT5OuFJWyYrbg1rr6tJqur6ng4rrglUy2tdJbIuCDg/edit#heading=h.o6074tuk59c9" target="_blank">https://docs.google.com/document/d/1zmT5OuFJWyYrbg1rr6tJqur6ng4rrglUy2tdJbIuCDg/edit#heading=h.o6074tuk59c9</a></div><div><br></div><div>So, for an AMx milestone build, we should mostly do option c (ship w/ a note), unless the milestone is REALLY unusable, in which case option b would apply.</div><div><br></div><div>How do you feel about this approach? </div><div><br></div><div>Nick</div><div><div><br></div><pre>_______________________________________________</pre><pre>jbosstools-dev mailing list</pre><pre><a href="mailto:jbosstools-dev@lists.jboss.org" target="_blank">jbosstools-dev@lists.jboss.org</a></pre><pre><a href="https://lists.jboss.org/mailman/listinfo/jbosstools-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/jbosstools-dev</a></pre></div></div></div></div></div></div></div>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:8pt;font-family:Arial;background-color:transparent;font-weight:400;font-style:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap"><font color="#999999">Nick Boldt</font></span></p><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:8pt;font-family:Arial;background-color:transparent;font-weight:400;font-style:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap"><font color="#999999">Principal Software Engineer, RHCSA</font></span></p><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:8pt;font-family:Arial;background-color:transparent;font-weight:400;font-style:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap"><font color="#999999">Productization Lead :: JBoss Tools & Dev Studio</font></span></p><p dir="ltr" style="line-height:1.2;margin-top:0pt;margin-bottom:3pt"><span><font color="#999999"><span style="font-size:8pt;font-family:Arial;background-color:transparent;vertical-align:baseline;white-space:pre-wrap">IM: @nickboldt / @nboldt / </span><span style="font-size:8pt;font-family:Arial;background-color:transparent;vertical-align:baseline;white-space:pre-wrap"><a href="http://nick.divbyzero.com" target="_blank">http://nick.divbyzero.com</a></span></font></span><br></p><div><div dir="ltr"><table border="0" style="color:rgb(0,0,0)"><tbody><tr><td width="100px"><a href="https://red.ht/sig" style="color:rgb(17,85,204)" target="_blank"><font face="arial, helvetica, sans-serif" size="1"><img src="https://www.redhat.com/files/brand/email/sig-redhat.png" width="90" height="auto"></font></a></td><td><div><a href="https://redhat.com/trusted" style="color:rgb(204,0,0);text-decoration:none;font-weight:bold" target="_blank"><font face="arial, helvetica, sans-serif" size="1">TRIED. TESTED. TRUSTED.</font></a></div></td></tr></tbody></table><div><div style="color:rgb(153,153,153)"><font face="arial, helvetica, sans-serif" size="1"><a href="https://twitter.com/redhatnews" title="twitter" style="color:rgb(119,119,119);background-image:url("https://www.redhat.com/files/brand/email/sm-twitter.png");height:20px;text-decoration:none;display:inline-block;line-height:20px;padding-left:16px;background-repeat:no-repeat;background-position:0px 50%" target="_blank">@ @redhatnews</a> </font><span style="color:rgb(153,153,153);background-image:url("https://www.redhat.com/files/brand/email/sm-facebook.png");height:20px;text-decoration:none;display:inline-block;line-height:20px;padding-left:16px;background-repeat:no-repeat;background-position:0px 50%;font-family:Arial;font-size:8pt;white-space:pre-wrap"><a href="https://www.facebook.com/RedHatInc" title="Facebook" style="color:rgb(119,119,119);background-image:url("https://www.redhat.com/files/brand/email/sm-facebook.png");height:20px;text-decoration:none;display:inline-block;line-height:20px;padding-left:16px;background-repeat:no-repeat;background-position:0px 50%" target="_blank"> Red Hat</a></span><a href="https://www.facebook.com/RedHatInc" title="Facebook" target="_blank"><br></a></div><div style="color:rgb(153,153,153)"><br></div><div><div><font color="#999999"><span style="font-size:12.8px"><br></span></font></div><div><font size="1"><font color="#999999">“The Only Thing That Is Constant Is Change” - </font><span style="color:rgb(153,153,153)">Heraclitus</span></font></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div>