Michael Meeks wrote: > Thankfully the code works :-) But the very concept of rampant > duplication of state all over the place is at root broken IMHO. Having > unnecessary screenshots, duplicating bi-lingual strings etc. adds > [AFAICS] nothing at all to an existing impl, but a huge amount of pain > in terms of re-synchronising things.
I don't want to argue against this, just a question: how should the QA find out wether the strings they find in the product are the right ones that others wanted to have there? I don't get how this works. > An asynchronous work-flow, whereby an Engineer can implement a > feature / fix, knock up a quick wiki page describing it, commit it to a > CWS, assign it to QA, mail the [email protected] list about it, and > get on with his next task would be ideal. Of course, U.E. could poke at > the wiki/issue (if they were interested & had time), otherwise it would > just proceed, QA likewise could ask questions / extend the wiki page > describing the change (if at all necessary), otherwise they could focus > on the real grist of the implementation. Interesting approach. I think we should check this against the goals behind the spec idea. > So - I'm not against writing -something- down, but lets make it > absolutely minimal. Matthias Heutsch had a nice flow based on the > Solaris process that included a streamlined fast track for > 'uncontroversial' changes; codifying that (and a load of timeouts for > comments) would substantially improve things. As we learned the hard way this great idea is pretty fast understood by developers, but obviously not well received by QA people. Apparently the degree of being "uncontroversial" for a particular change depends on the previous knowledge and the skills of the participants in the dispute. That's the dilemma. I remember the meeting where we discussed this idea and we all thought that this a great thing. Perhaps it's time to advertize it more aggressively. It won't help you with your general "spec phobia" though. Ciao, Mathias -- Mathias Bauer - OpenOffice.org Application Framework Project Lead Please reply to the list only, [EMAIL PROTECTED] is a spam sink. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
