defaria.com/blogs/Status/archives/000526.html

   1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
   2    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
   3 <html xmlns="http://www.w3.org/1999/xhtml" id="sixapart-standard">
   4 <head>
   5    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
   6    <meta name="generator" content="Movable Type 5.2.3" />
   7
   8    <link rel="stylesheet" href="http://defaria.com/blogs/Status/styles-site.css" type="text/css" />
   9    <link rel="alternate" type="application/atom+xml" title="Atom" href="http://defaria.com/blogs/Status/atom.xml" />
  10    <link rel="alternate" type="application/rss+xml" title="RSS 2.0" href="http://defaria.com/blogs/Status/index.xml" />
  11
  12    <title>Status for Andrew DeFaria: MobMM Completion</title>
  13
  14    <link rel="start" href="http://defaria.com/blogs/Status/" title="Home" />
  15    <link rel="prev" href="http://defaria.com/blogs/Status/archives/000525.html" title="MobMM email" />
  16    <link rel="next" href="http://defaria.com/blogs/Status/archives/000527.html" title="Final MobMM Issues" />
  17
  18
  19
  20
  21
  22    <script type="text/javascript" src="http://defaria.com/blogs/Status/mt-site.js"></script>
  23 </head>
  24 <body class="layout-one-column" onload="individualArchivesOnLoad(commenter_name)">
  25    <div id="container">
  26       <div id="container-inner" class="pkg">
  27
  28          <div id="banner">
  29             <div id="banner-inner" class="pkg">
  30                <h1 id="banner-header"><a href="http://defaria.com/blogs/Status/" accesskey="1">Status for Andrew DeFaria</a></h1>
  31                <h2 id="banner-description">Searchable status reports and work log</h2>
  32             </div>
  33          </div>
  34
  35          <div id="pagebody">
  36             <div id="pagebody-inner" class="pkg">
  37                <div id="alpha">
  38                   <div id="alpha-inner" class="pkg">
  39
  40                      <p class="content-nav">
  41                         <a href="http://defaria.com/blogs/Status/archives/000525.html">&laquo; MobMM email</a> |
  42                         <a href="http://defaria.com/blogs/Status/">Main</a>
  43                         | <a href="http://defaria.com/blogs/Status/archives/000527.html">Final MobMM Issues &raquo;</a>
  44                      </p>
  45
  46                      <a id="a000526"></a>
  47                      <div class="entry" id="entry-526">
  48                         <h3 class="entry-header">MobMM Completion</h3>
  49                         <div class="entry-content">
  50                            <div class="entry-body">
  51                               <ul>
  52   <li>Reached code completion level for MobMM</li>
  53 </ul>
  54                            </div>
  55                            <div id="more" class="entry-more">
  56                               <h2>Remaining issues</h2>
  57
  58 <p>I see only a few remaining issues to be code complete and that is to implement the CC list. I'm trying to implement it as a box with a "..." button that has a dialog that walks you through entering lines of text. Not sure if I can validate those lines to &lt;user&gt;@&lt;domain&gt;.&lt;tld&gt;. Once that's done I just need to add code to SendEmail to parse CC, separate by newlines and push the email addresses onto the recipients array. The rest of the code will already handle sending out email. (Note there's currently a flag field there called Testing which is set to true. Having it set to true says "Send out email only to  adefaria@broadcom.com". I didn't think it wise to be sending out test email to real people right yet - it'd only confuse them. We just need to either set Testing = false or remove the test code for production).</p>
  59
  60 <p>There is also the issue of a script, triggered to run when a Perforce user checks in, to update changeset. I could write a Perl module that has a simple function to update MobMM's changeset (e.g. UpdateMMChangeset (&lt;id&gt;, &lt;changeset&gt;)) then the implementer for the Perforce trigger need only use the module and call the procedure. Ray let me know if you want that.</p>
  61
  62 <p>Other than that this project would be "code complete". Things that still need to be done for production would be:</p>
  63
  64 <ol>
  65   <li>Set up production server (I believe this is in progress)</li>
  66
  67   <li>Create production DBs</li>
  68
  69   <li>Upgrade DBs with user accounts</li>
  70
  71   <li>Setup CQ Web</li>
  72
  73   <li>Disseminate Clearquest software to those who wish to use Clearquest Client</li>
  74 </ol>
  75                            </div>
  76                         </div>
  77                         <p class="entry-footer">
  78                            <span class="post-footers">Posted by  on January 30, 2006 10:07 AM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000526.html">Permalink</a>
  79                         </p>
  80                      </div>
  81
  82
  83
  84
  85                   </div>
  86                </div>
  87             </div>
  88          </div>
  89       </div>
  90    </div>
  91 </body>
  92 </html>