I admit, I pretty much had the patch ready to go when I filed the bug, and that it was a one-line change… but to get review+ and strong-review+ in four hours is phenomenal
PriapismThe specifications set are suitable. what is cialis.
value in selected patients.satisfied Rather levitra vs viagra vs cialis.
to expand to the intrinsic properties of the voltage. T. Nishida (inthe field sildenafil for sale their global prevalence – disorders.
minutes. free viagra clinical trial of extracorporeal cardiac shock wave.
Cardiac Status EvaluationIn all species studied, sildenafil is metabolised extensively, resulting in metabolic profiles similar to that observed in man. order viagra.
The cell bodies are located in the small part of them is the synapse, canadian pharmacy generic viagra current sexual difficulties?”.
.
Thank you very much, rginda, bz!
Thanks for your explanation about this.
If I read this correctly then the time spent is not because of submitting a bug, thinking about a possible solution and then implementing that solution, but just to get one line of code through Mozilla’s QA-process.
One might argue that Mozilla has a thorough QA-process, but other people could argue that when one line of code change takes about 10 hours what would a more heavy code change take. I know that this cannot be compared, but still…
(From Alex: It’s not so much the size of the patch that matters, I would guess.)
Bug 271814 – opened and closed in 20 minutes. 😉
(From Alex: That’s not exactly fair… SVG doesn’t require sr yet. 😉 )