Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [dsdp-tm-dev] TM IP Log Double Bookkeeping

Martin --

Yes this does pay off. I hear that other projects really have to scramble sometimes to get their logs updated for this review. Thanks for staying on our case.

-- Dave

On May 13, 2008, at 7:14 PM, Oberhuber, Martin wrote:

Dear TM Committers,
 
Since a "frozen" version of our IP Log needs to be sent in to Eclipse Legal
by Thursday COB, I reviewed our double bookkeeping to find any inconsistencies
between bugzilla and our manual tm-log.csv.
 
You might be interested in hearing that I found several inconsistencies:
  • 1 typo in the bugzilla number  in tm-log.csv
  • 2 contributed patches not mentioned in tm-log.csv
  • 2 bugzilla bugs with contributed patches but not yet marked FIXED
  • 2 bugzilla bugs with contributed patches but without "contributed" kwd
  • 2 bugzilla bugs with rogue "contributed" kwd where nothing had actually been contributed (this happens sometimes when cloning a bug)
You see that it pays off to do the double bookkeeping.
Please make sure that we continue doing it with utmost diligence!
 
Thanks,
--
Martin Oberhuber, Senior Member of Technical Staff, Wind River
Target Management Project Lead, DSDP PMC Member
 
 
_______________________________________________
dsdp-tm-dev mailing list
dsdp-tm-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dsdp-tm-dev


Back to the top