defaria.com/blogs/Status/archives/week_2006_01_29.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: January 29, 2006 - February  4, 2006 Archives</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/week_2006_01_22.html" title="January 22, 2006 - January 28, 2006" />
  16    <link rel="next" href="http://defaria.com/blogs/Status/archives/week_2006_02_05.html" title="February  5, 2006 - February 11, 2006" />
  17 </head>
  18 <body class="layout-one-column">
  19    <div id="container">
  20       <div id="container-inner" class="pkg">
  21
  22          <div id="banner">
  23             <div id="banner-inner" class="pkg">
  24                <h1 id="banner-header"><a href="http://defaria.com/blogs/Status/" accesskey="1">Status for Andrew DeFaria</a></h1>
  25                <h2 id="banner-description">Searchable status reports and work log</h2>
  26             </div>
  27          </div>
  28
  29          <div id="pagebody">
  30             <div id="pagebody-inner" class="pkg">
  31                <div id="alpha">
  32                   <div id="alpha-inner" class="pkg">
  33
  34                      <p class="content-nav">
  35                         <a href="http://defaria.com/blogs/Status/archives/week_2006_01_22.html">&laquo; January 22, 2006 - January 28, 2006</a> |
  36                         <a href="http://defaria.com/blogs/Status/">Main</a>
  37                         | <a href="http://defaria.com/blogs/Status/archives/week_2006_02_05.html">February  5, 2006 - February 11, 2006 &raquo;</a>
  38                      </p>
  39
  40
  41
  42
  43                      <h2 class="date-header">January 31, 2006</h2>
  44                      <a id="a000527"></a>
  45                      <div class="entry" id="entry-527">
  46                         <h3 class="entry-header">Final MobMM Issues</h3>
  47                         <div class="entry-content">
  48                            <div class="entry-body">
  49                               <ul>
  50   <li>Resolved issue with MsgBox not being executed for the web</li>
  51
  52   <li>Still have problem with IE and certain drop down boxes</li>
  53
  54   <li>Worked with John Luu to get the web server running on nt-irva-0458. We need to have a database instance created and to move this schema and user databases to that server. Why is the web server in Ivrine when the group is in San Jose?</lI>
  55
  56                               <h2>IE and drop down boxes</h2>
  57
  58 <p>Jean had reported that certain fields on the Resolution tab did not work. They do work, in the client and using Firefox but indeed don't work in IE. At first I thought that this was a problem with the JRE so I tried installing the latest. That did not solve the problem.</p>
  59
  60 <p>IE seems to have a bona fide problem with the new CQJW and certain fiels. I scoured the Rational Formus to no avail. A defect will need to be submitted to Rational for this. I did not submit one because the follow up would be to me and probably should be to John.</p>
  61
  62 <p>It is not just the fields on the Resolution tab that are causing problems, fields on the Verification tab as well as some fields on the Submission tab (e.g. Hardware Platform).</p>
  63
  64
  65
  66                               <p class="entry-footer">
  67                                  <span class="post-footers">Posted by  at  3:30 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000527.html">Permalink</a>
  68
  69
  70                               </p>
  71                            </div>
  72                         </div>
  73                      </div>
  74
  75
  76
  77                      <h2 class="date-header">January 30, 2006</h2>
  78                      <a id="a000526"></a>
  79                      <div class="entry" id="entry-526">
  80                         <h3 class="entry-header">MobMM Completion</h3>
  81                         <div class="entry-content">
  82                            <div class="entry-body">
  83                               <ul>
  84   <li>Reached code completion level for MobMM</li>
  85 </ul>
  86
  87                               <h2>Remaining issues</h2>
  88
  89 <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>
  90
  91 <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>
  92
  93 <p>Other than that this project would be "code complete". Things that still need to be done for production would be:</p>
  94
  95 <ol>
  96   <li>Set up production server (I believe this is in progress)</li>
  97
  98   <li>Create production DBs</li>
  99
 100   <li>Upgrade DBs with user accounts</li>
 101
 102   <li>Setup CQ Web</li>
 103
 104   <li>Disseminate Clearquest software to those who wish to use Clearquest Client</li>
 105 </ol>
 106
 107                               <p class="entry-footer">
 108                                  <span class="post-footers">Posted by  at 10:07 AM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000526.html">Permalink</a>
 109
 110
 111                               </p>
 112                            </div>
 113                         </div>
 114                      </div>
 115
 116                   </div>
 117                </div>
 118             </div>
 119          </div>
 120       </div>
 121    </div>
 122 </body>
 123 </html>