<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">On Mar 19, 2015, at 2:00 PM, Arnaud Quette <<a href="mailto:arnaud.quette@gmail.com">arnaud.quette@gmail.com</a>> wrote:<br><div><br class="Apple-interchange-newline"><blockquote type="cite"><span style="font-family: Helvetica; font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;">So is everything good to go from your PoV Charles?</span><br style="font-family: Helvetica; font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"></blockquote></div><div><br></div><div>Yes, except if we aren't going to fix the NSS SSL issue for this release, we should do two things before releasing:</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>• Add a note to UPGRADING explaining the problem and the -D workaround</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>• Branch and plan to release 2.7.3.1 (or similar) once we fix it</div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px;"><div>-- </div><div>Charles Lepple</div><div>clepple@gmail</div><div><br></div></span><br class="Apple-interchange-newline">
</div>
<br></body></html>