Page MenuHomeLubuntu Development

Where to report bugs is unclear
Closed, ResolvedPublic

Description

The release notes of 19.10 said I should look in the wiki if I had found bugs. I did and it said I should report my bugs on launchpad. On launchpad, the last Lubuntu team package was Lubuntu-meta for Bionic. I report this bug here since everything has moved to phabricator if I have understood it correctly.

Event Timeline

The release notes link to the Bugs page. If you got to that, the short answer to how is in the "How to report bugs" section. What follows immediately after is a list of packages to file against. That seems pretty clear to me, so what do you think needs improved specifically? What specific questions aren't answered or how did you miss it?

This release page (https://lubuntu.me/eoan-released/) says under bugs: Another great method to get involved is bug reporting. If you notice an issue, please file a bug using the instructions on the Lubuntu Wiki. The Lubuntu Wiki link brings me to this page: https://phab.lubuntu.me/w/bugs/ It explains that you need a launchpad account and how to file a bug on launchpad. Aren't we supposed to report bugs on phabricator now?

Hi @EinarMostad

First of all, thank you, that you have started writing bug reports.

It explains that you need a launchpad account and how to file a bug on launchpad. Aren't we supposed to report bugs on phabricator now?

For normal users, it is better, if they file bug reports on launchpad and link them to a Lubuntu package, so that we should see the report. Writing a bug report on launchpad has several advantages:

  • Other users can find them, when looking for a bug on launchpad
  • If we intend to fix it also in a current stable release (Stable Release Update SRU), we can use an existing bug report on launchpad, instead of creating one
  • Maybe the bug is not caused by our package, so we can link it to another package
  • We can point to the launchpad bug in the changelog

We use Phabricator to track the development status and because it is easier to write and format posts. We use the tasks also to collect the links to launchpad, upstream issues, etc. It is common, that several reports on several platforms exist for the same bug.

D'oh! I have completely misunderstood the move to phabricator. I am sorry for wasting your time! (Maybe the wiki shold mention that Phabricator is only used to track development so others can avoid the same misunderstanding.)

D'oh! I have completely misunderstood the move to phabricator.

Yes and no. Phabricator is in some cases the best place to file bugs and reports, for example this task or T127. In other cases, Launchpad or Github are better, e.g. for T125.

I am sorry for wasting your time!

You don't waste our time! At the end, maybe it is the same developer or packager, that is working with your bug report, independently if it is written on Phab or Launchpad.

(Maybe the wiki shold mention that Phabricator is only used to track development so others can avoid the same misunderstanding.)

Maybe you are right.

@EinarMostad could you please check the Bugs page again? I made a bunch of changes that I think should clarify things:

  1. moved all the wordy documentation about making effective bug reports down
  2. made a very 5-point list right at the top on how to report a bug
  3. made sure that the list item dealing with reporting the bug references the package list that follows
  4. made sure that there is a list item that references the aforementioned wordy documentation
  5. made the note more clear that if a bug is to be reported and it's unclear what the package is, to file against lubuntu-meta
  6. most relevant to your concern, the list item dealing with getting a Launchpad account clarifies that bug tracking is done there and Phabricator is used for development tasks.

Additionally I changed the preamble on the new task form to clarify this point as well, with a link to the bugs page.

Thank you! It is much clearer now.

Thank you for bringing this up and helping us resolve it.