In a previous instance of the APAC meeting of the Gluster community I had mentioned about looking at the component update section and considering providing a report on the untriaged bug load. The rationale is to ensure that instead of a large mess of "unknown" bugs, the maintainers (and thus the project) take a look at the weekly report that is generated and begin to take steps to control the growing number of untriaged one. In the meeting today/14Jan, Hari pointed out that the request should be more widely circulated than an entry in the meeting minutes. And hence this note. The triage activity would also help frame the upcoming release(s) in context of how many reported bugs were addressed in the release and other meta-data around the same eg. how long it took the project to get it into a release. _______________________________________________ Community Meeting Calendar: APAC Schedule - Every 2nd and 4th Tuesday at 11:30 AM IST Bridge: https://bluejeans.com/441850968 NA/EMEA Schedule - Every 1st and 3rd Tuesday at 01:00 PM EDT Bridge: https://bluejeans.com/441850968 Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-devel
