3.5.3rc1 win32 / debug package ...

[bfo]

On Fri, May 25, 2012 at 3:21 PM, Petr Mladek - pmladek at suse.cz wrote:
> We are already using Litmus and are going to migrate to Moztrap. Though,
> we are not familiar with the real processes that used in the Mozilla
> project.
> Do you have any experience with the Mozilla processes? Are you able to
> compare it with the current LibreOffice processes that are described at
> http://wiki.documentfoundation.org/QA ?
> This is the area where we really need improvements.

It would be difficult for me to compare it, as I am not a QA/RelEng
specialist, insider nor involved in the process.
I think you should just check what they achieved at these sites in
terms of workflow, automation and data gathering:

https://quality.mozilla.org/
https://wiki.mozilla.org/QA/Desktop_Firefox
https://wiki.mozilla.org/Socorro
https://crash-stats.mozilla.com/products/Firefox
https://tbpl.mozilla.org/

http://www.mozilla.org/hacking/module-ownership.html
https://wiki.mozilla.org/Modules
http://www.mozilla.org/hacking/committer/
http://www.mozilla.org/hacking/reviewers.html
https://wiki.mozilla.org/Sheriff_Duty
https://wiki.mozilla.org/ReleaseEngineering:Sheriffing
http://www.mozilla.org/hacking/regression-policy.html
https://wiki.mozilla.org/Inbound_Sheriff_Duty

One have to remember that Mozilla have full time QA employees and
build those tools for years.
They changed release cycle recently and also had some problems (being
so experienced).
As LibreOffice is complicated project maybe you should implement some
more automation and crash data gathering.
I read that you have unused reporting tool in the codebase and plans
to bring it back to life. Without it do you know the top crashers? 
Per platform? Per branch? I do not see such information in ESC minutes
 (btw: could you put them also in the wiki?).
Depending just on Bugzilla queries IMHO is not enough.
Also I am really concerned about your QA priorities. IMHO you should
care little more about Windows builds and MS Office filters.
Without those it will be a huge problem to gain users on this
platform. Unfortunately Windows support and MS format regressions are
little scary. I am not a developer, but Microsoft published the
documentation at
http://msdn.microsoft.com/en-us/openspecifications/cc816059.aspx. 
Unfortunately changes in the Microsoft policy about compilers
(http://arstechnica.com/information-technology/2012/05/no-cost-desktop-software-development-is-dead-on-windows-8/)
can discourage Windows volunteers or developers even more....
And no - buy support, pay for code, do it yourself or change OS is not the
right answer.

> It would be great if you could join us and discus particular changes on
> the libreoffice-qa
> mailing list.

Sadly I'm not QA specialist. I just decided to help LO project by
confirming as many bugs as I can find in Bugzilla. Hope this will help
increase the quality of LO for
Windows in any way...

Best regards.


--
View this message in context: http://nabble.documentfoundation.org/Re-3-5-3rc1-win32-debug-package-tp3984895p3986061.html
Sent from the Dev mailing list archive at Nabble.com.