<br><br><div><span class="gmail_quote">On 6/21/06, <b class="gmail_sendername">Deb Lewis</b> <<a href="mailto:dlewis@glaivestone.com">dlewis@glaivestone.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>
<div>
<div dir="ltr" align="left"><font color="#0000ff" face="Arial" size="2"><span>Yep, lost some of the changes I put in late yesterday
morning in the doc files. I'll recheck all the changes I put in yesterday
morning (doc files and some changes in release notes,change
log...)</span></font></div></div></div></blockquote><div><br>Sounds great, just let me know when things are ready and we can do the release then.<br> </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div><div dir="ltr" align="left"><font color="#0000ff" face="Arial" size="2"><span>Upgrading and reinstalling my firewall seems to have
solved the baffling problems I've been having since last week with file edits
not resulting in updated mtimes. grrrr....</span></font></div>
<div dir="ltr" align="left"><font color="#0000ff" face="Arial" size="2"><span></span></font> </div>
<div dir="ltr" align="left"><font color="#0000ff" face="Arial" size="2"><span>One more thought about the release message: we should
include a short note on upgrading from prev. release of MV, existing users
*must* redo their config setups if customized and need to review where their
template files live. </span></font></div></div></div></blockquote><div><br>Yes, I will add something about that.<br> </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div><div dir="ltr" align="left"><font color="#0000ff" face="Arial" size="2"><span>We need to have a stable url that we can point to where
the latest release's release note are posted so users always have a reliable
place to go to get a preview of changes and upgrade notes before picking up new
build. Drive me nuts when packages don't provide this info (well geez...
what happened and do I need to know anything important before I install newer
version??)</span></font></div></div></div></blockquote><div><br>Agreed. Our change_log will be a living document, but it probably doesn't have the details needed for what you described. <br> </div><br></div><br>