Hi, Thanks Eike and Niklas. It would take me ages to resync msba01 to src680 (since I have a very slow internet connection). But, since i56202 is a small one - is it really necessary? If it is then re-cws'ing (download source, create new cws, commit) is much faster for me. (or if somebody helps me resync it!)
Btw, can I re-use msba01 in case I decide (or rather get no-option than) to 're-cws'? I thought owner was set automatically! Sorry, will set it correctly. Regards, Muthu Subramanian ---------- Forwarded message ---------- From: Eike Rathke <[EMAIL PROTECTED]> To: [email protected] Date: Thu, 31 May 2007 13:17:51 +0200 Subject: Re: [sc-dev] Whom should I assign i56202 to (for QA)? Hi Muthu, On Monday, 2007-05-28 21:51:39 +0530, Muthu Subramanian wrote:
I fixed i56202 in msba01. [ http://www.openoffice.org/issues/show_bug.cgi?id=56202]
Beside being on the wrong branch and needs to be resynced to SRC680, as Niklas already mentioned, the CWS lacks the following information, that is to be filled in the EIS application: - Owner, (!) probably because that is not set the CWS also doesn't show up in the list of CWSs that "SeekQA". - Description, what the CWS is about. - Release, you should set that to OOo2.3 if that's the target). - Estimated due date "ready for QA" (when the CWS approximately will be ready for QA. This is to give QA an idea when the CWS will be ready. - Estimated due date, when the CWS should be ready for integration. Note that the time span between ready-for-QA date and the final due date needs to be communicated with the QA-rep. This is to give release engineering an idea when a CWS will show up for integration. - Level of impact, in this case "One Application". After having resynced to the latests SRC680 milestone you'll have to build install sets QA can use. Talk with the QA-rep (see below) what he'll accept. As a new feature/enhancement is implemented, you'll have to send a feature announcement, in EIS that's under Changes-Mails -> external feature. - Product: Spreadsheet - Type: new - Title: make up a good one, self-speaking - Effective from version: CWS msba01 - Module(s) affected: sc - Flags: select Configuration, Help/Guide, Translation, UI relevant - TaskId: i56202 - Description: describe the feature such that QA can test the feature, documentation authors are able to digest the necessary information for the online help system, and the description can also be taken for the automated "what's new" guide. - Specification URL: - (a literal minus/hyphen character, as the feature doesn't have an external specification document)
Whom should I 'assign to', in EIS, for QA?
For Calc QA, you may ask Frank Stecher <[EMAIL PROTECTED]> or Oliver Craemer <[EMAIL PROTECTED]> if they can do QA or know someone who would.
Next time, how do I find out whom to assign it to (when I fix some other issue)?
Get in contact with the project's dev-list, or ask on [EMAIL PROTECTED] As mentioned above, if proper information is filled in EIS, the CWS is also listed under SeekQA and someone might jump on it. Eike -- OOo/SO Calc core developer. Number formatter stricken i18n transpositionizer. OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't send personal mail to this [EMAIL PROTECTED] account, which I use for mailing lists only and don't read from outside Sun. Thanks.
