Bug tracker

nopro404 · 2018-08-26T12:26:02.598Z

Can I suggest GL-Inet setup a bug tracker?

It would be much easier to find and track bugs and subscribe to them to be notified of fixes.

Johnex · 2018-08-26T13:20:42.901Z

It would be great if GL sets up a bug tracker so we can post our bugs, and also see what is being worked on in the background. When a bug or feature is being worked on internally, it can be added to the bug tracker so we can see the progress too.

alzhao · 2018-08-28T07:14:09.345Z

Do you have a recommendation of a lightweight and easy to use bug tracker system?

Johnex · 2018-08-28T10:47:41.094Z

OpenWRT uses Flyspray:

flyspray.org

Flyspray : Flyspray: The bug killer!

The bug killer!

GitHub

Issues · openwrt/openwrt

This repository is a mirror of https://git.openwrt.org/openwrt/openwrt.git It is for reference only and is not active for check-ins. We will continue to accept Pull Requests here. They will be mer...

alzhao · 2018-08-28T10:48:05.054Z

I saw that. Looks much better than bugzilla.

Johnex · 2018-08-28T10:50:34.890Z

There is also trac. Unfortunately both flyspray and trac and even bugzilla are not fully integrated, they need the webserver and so on configured separately, so not like this discourse forum system that is fully integrated.

Johnex · 2018-08-28T10:53:21.417Z

MantisBT is pretty sweet. It’s the equivalent of this forum lets say, with Markup and lets you post images and so on.

Take a look:

https://www.mantisbt.org/bugs/my_view_page.php

mantisbt.org

Mantis Bug Tracker

MantisBT is a popular free web-based bug tracking system. It is written in PHP works with MySQL, MS SQL, and PostgreSQL databases. MantisBT has been installed on Windows, Linux, Mac OS, OS/2, and others. It is released under the terms of the GNU...

nopro404 · 2018-08-28T10:58:10.488Z

I think it makes sense to use the GitHub issue tracker associated with the imagebuilder repos.

Make a pinned post in the software section. List all the models of the same hardware type then link the various imagebuilders and their associated issue trackers.

Something like:

Supported Model	Software	Version	Firmware	Links	Notes
AR300M AR300M-EXT	GL.iNet	2.27	GL.iNet NAND	NAND Image Builder NAND Issue Tracker NAND Wiki	Latest Version
AR300M AR300M-EXT AR300M-LITE	GL.iNet	2.27	GL.iNet NOR	NOR Image Builder NOR Issue Tracker NOR Wiki	Latest Version

Johnex · 2018-08-28T11:02:48.090Z

I think using a dedicated bugtracker would be better.
GL will be able to set up road maps for release of routers and firmware also, apart from bugs and features.

The UI of the routers is not open source, so it would be strange to have bug reporting for the UI in one repo, and then bugs for each imagebuilder too…

I think it would be best to put it all in one place. GL will be able to internally start using the bug tracker too, instead of the solution they are using at the moment. Their developer team would not want to be using github for reporting progress i don’t think, and like above there would be too many urls and so on to keep track of.

nopro404 · 2018-08-28T11:22:45.379Z

Good points. I was just going for the path of least resistance. A lot of people already have GitHub accounts, and the issue tracker is already there, no need to set one up, host, care and feed it.

If you want to go that route, FlySpray seems good. If you’re going to set something up though, go for a GitLab instance, get the full build system going with build releases and the bug tracker, wiki etc. Or pay for SaaS GitHub/GitLab.