The list you come up gives good ideas on what
could be included. But, I afraid it would be far too 
much work, if it is what "must" done and if I am
the only one doing it. Likely, I am the only one.

I think it is much more practical for me to find
two hours and fill the bugzilla at once for all items. 
Spending an hour each, means the list will only be 
finished in months later. For instance, listing
possible approaches may require me to look at 
the code for half an hour each already.

But, again, your lists good idea on what could be 
included. Thank!



Thomas


-----Original Message-----
>From: Werner Guttmann [mailto:[EMAIL PROTECTED]]
>Sent: Friday, April 26, 2002 3:46 AM
>To: [EMAIL PROTECTED]
>Subject: Re: [castor-dev] Castor JDO Status
>
>Great. Thomas, I am really glad to see that we have your committment
>here. Now, as you are project lead on Castor JDO, how do you feel about
>taking the list of items you posted under the same subject the other day
>and add them to BugZilla .. incl. a description that tries to be as
>complete as possible. I know you are very short on time, but as you are
>the project lead, the main patch reviewer - in other words, the person on
>this project with the most detailed understanding - I guess there's no
>alternative.
>
>I'd would be really nice if we eventually had - for all the items in your
>list at least - not only the bug/feature request/change request entry in
>Bugzilla, but maybe additional information such as ...
>
>a) a short decription of repeatable test cases so tha tothers could
>reproduce this.
>b) a short problem description (from a users experience)
>c) an description of where Castor might be having a problem here, and
>what areas of the code need to be addressed to solve this.
>d) possible approches
>
>Thomas, what do you think ?
>
>Werner
>
>Thomas Yip wrote:
>
>> I second Bruce proposal to put those information
>> on the bugzilla.
>>
>> Thomas
>>
>> >That is *exactly* why I suggested putting all this stuff into
>> >Bugzilla. It's really the only true living artifact on the web site.
>> >The web site itself does not get updated very often because it
>> >requires intervention from people at Intalio. Bugzilla, however,
>> >can be updated by anyone with an account (committers). It doesn't
>> >require an Intalio sys admin. Also, it allows anyone to execute
>> >queries because they're read-only. Additionally, committers could
>> >place notes about defects/enhancements in one place that can be
>> >updated at any time and that can be viewed by all.
>> >
>> >Bruce
>> >--
>> >
>> >perl -e 'print
>> unpack("u30","<0G)U8V4\@4VYY9&5R\"F9E<G)E=\$\!F<FEI+F-O;0\`\`");'
>> >
>> >-----------------------------------------------------------
>> >If you wish to unsubscribe from this mailing, send mail to
>> >[EMAIL PROTECTED] with a subject of:
>> >        unsubscribe castor-dev
>> >
>>
>> -----------------------------------------------------------
>> If you wish to unsubscribe from this mailing, send mail to
>> [EMAIL PROTECTED] with a subject of:
>>         unsubscribe castor-dev
>
>-----------------------------------------------------------
>If you wish to unsubscribe from this mailing, send mail to
>[EMAIL PROTECTED] with a subject of:
>        unsubscribe castor-dev 
>

----------------------------------------------------------- 
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
        unsubscribe castor-dev

Reply via email to