libreoffice team mailing list archive
-
libreoffice team
-
Mailing list archive
-
Message #00013
Re: LibreOffice in Ubuntu Triage Upstream Policy Inquiry
On Mon, Jul 30, 2012 at 11:26:19AM -0400, Christopher Penalver wrote:
> Hello everyone. I wanted to inquire on the current LibreOffice in Ubuntu triage upstream policy.
>
> In past triaging efforts, I have been testing for bugs in the latest release available in Ubuntu. Due to how LibreOffice in Ubuntu differs very little from upstream, I then referred Triaged bug reports upstream.
>
> However, room for improvment in triaging seems available. For example, in Linux (Ubuntu) a triager will not advise the reporter to send it upstream until the mainline kernel is tested. This accomplishes many goals. First, it tests to make sure that a Ubuntu patch did not cause the problem. Second, it gives the Ubuntu developer more data points as the mainline is always a higher release version then that available in the Ubuntu repository. Third, it opens the bug up further to upstream developers. Fourth, it better pleases upstream developers who want it tested in the newest release of their kernel, not Ubuntu's.
>
> So, the following article:
> https://wiki.ubuntu.com/LibreOfficeBugWrangling#How_to_Forward_Bugs_Upstream
>
> could be improved by mentioning how one should test in the newest release available from http://www.libreoffice.org/download/ . However, a cautionary advisory would want to be provided, noting one should fully remove all libreoffice (Ubuntu) components and any universe (ex. lo-menubar) and 3rd party extensions, or it could spoil the test. Of course, since this is userspace, triagers have more of an opportunity to test for the problem then with the kernel, which tends to be highly hardware dependent.
>
> What do you think?
Upstream LibreOffice is seriously considering not providing "universal"
binaries for Linux in the near future and leave the building to the distros.
So, IMHO we should put such a decision on hold for now.
http://wiki.documentfoundation.org/QA/HowToBibisect
is a upstream solution to hunt down when a regression was introduced and
http://nabble.documentfoundation.org/Adding-bibisect-repository-support-to-tinbuild2-td3996707.html
talks about integrating bibisect with tinbuild (the upstream tinderboxes at
http://tinderbox.libreoffice.org/MASTER/status.html).
If so, we should have a tinderbox building for Ubuntu and use that as the
canonical way of upstream testing.
Just my 2 euro cent -- Best,
Bjoern
References