search for: triaged

...f someone could put together a bug triage guide and put it on the wiki. I was looking for something to do tonight and z00dax said go hunt some bugs. So I went first to the wiki to look for a guide for a proper procedure on how the team would like bug triaging handled but didn't find one. I have triaged before but i know every place is different. So some guidelines would come in handy, thanks. -- LostSon http://lostsonsvault.org CentOS - It's not just for servers ya know... -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pg...

As everyone probably realizes, I''m getting swamped with incoming problems and tickets and I still need help triaging the tickets. James Turnbull has volunteered to help some, but I think we need more than one person. We''ve had a few people step in once or twice, but I''d like to be able to depend on Unreviewed tickets getting handled by someone else, rather

...provided ideas and feedback for this! With there now being a description of what is expected during bug triaging (http://llvm.org/docs/BugLifeCycle.html#triaging-bugs), we're looking for more volunteers to actually do the bug triaging. About half of all raised bugs currently don’t seem to get triaged. The idea is to have one or more volunteers for each of the well over 100 different product/component combinations we have in bugzilla. If you volunteer to help with triaging bugs against a specific component, we’ll add you to the default cc list for that component, so that when a new bug is raise...

...And thanks for re-raising the question whether we have the right components in bugzilla. As I think this could be an area for lots of different opinions, without any near-perfect solution, it has the potential to be a discussion that drags on for a long time. I thought half of all bugs not getting triaged was a serious enough problem to try and tackle first (with this mail thread) before aiming to improve the component breakdown in bugzilla. I think that setting default-cc lists on the components we have currently is largely orthogonal to reducing/merging components, as we can always merge default-c...

...And thanks for re-raising the question whether we have the right components in bugzilla. As I think this could be an area for lots of different opinions, without any near-perfect solution, it has the potential to be a discussion that drags on for a long time. I thought half of all bugs not getting triaged was a serious enough problem to try and tackle first (with this mail thread) before aiming to improve the component breakdown in bugzilla. I think that setting default-cc lists on the components we have currently is largely orthogonal to reducing/merging components, as we can always merge default-c...

On Mon, Aug 28, 2017 at 8:04 AM, Alex Bradbury <asb at asbradbury.org> wrote: > On 27 August 2017 at 00:01, Alex Bradbury <asb at asbradbury.org> wrote: >> Hi all. I'm assuming most people reading this email are familiar with LLVM's >> code review process <http://llvm.org/docs/DeveloperPolicy.html#code-reviews> >> as well as LLVM Weekly, the

...>>> components in bugzilla. >>> As I think this could be an area for lots of different opinions, without >>> any near-perfect solution, it has the potential to be a discussion that >>> drags on for a long time. >>> I thought half of all bugs not getting triaged was a serious enough >>> problem to try and tackle first (with this mail thread) before aiming to >>> improve the component breakdown in bugzilla. >>> I think that setting default-cc lists on the components we have >>> currently is largely orthogonal to reducing/...

We held a round-table at the llvm dev conference about what other pieces of Github infrastructure we may want to use. This thread in particular is about switching to github issue tracking. Use of other parts of Github functionality was also discussed -- but that should be for other email threads. Most of the ideas here were from other people. I *believe* this proposal represents the overall

Evening, Alright folks, as Jeremy Kemper mentioned I''m working on a set of "triage" scripts for the Rails trac using RFuzz to go through all the tickets and clean them out. I''ve talked this over with the core guys, and they''re behind it. I''m calling this set of scripts "THE MAGGOT" thanks to hasmanyjosh. Basically THE MAGGOT (all caps)

Evening, Alright folks, as Jeremy Kemper mentioned I''m working on a set of "triage" scripts for the Rails trac using RFuzz to go through all the tickets and clean them out. I''ve talked this over with the core guys, and they''re behind it. I''m calling this set of scripts "THE MAGGOT" thanks to hasmanyjosh. Basically THE MAGGOT (all caps)

Back in February, I opened two bugs, that seem to have had no activity: https://bugs.centos.org/view.php?id=15850 https://bugs.centos.org/view.php?id=15846 Is there some step I skipped when creating these? Or am I being impatient? :) -- Brian Reichert <reichert at numachi.com> BSD admin/developer at large

Hey Guys, All the tickets in our database now have a milestone of 1.0 or 1.x. The current plan is to fix all the 1.0 blockers before the 1.0 release and leave the 1.x defects till later. To view the list of blockers you need this report http://dev.rubyonrails.org/report/9 Now, as we''re all pragmatic programmers the next step should be to create unit tests that expose each of those

...gt; 14 bugs every day. > > Since June 1st: > - 412 total bugs filed > - 87 bugs resolved invalid > - 227 bugs resolved fixed > - 133 bugs confirmed but not resolved (status new) > - 292 bugs created but unconfirmed > > Doing some subtraction that means we have 292 new untriaged bugs, but we > triaged or fixed (412-292-87-227-133) = 327 old bugs. > > So, we're swimming above water, which is good. But at this rate it'll > be years before we triage every bug. So, let's do something :) > > > Bug Jam this Monday! > > One idea that h...

Hi, I think that there are a few bugs that can be closed or that are less severe than the time of submission. http://bugs.freedesktop.org/show_bug.cgi?id=12361 This one does work for me, if anyone can confirm that i believe this is fixed. http://bugs.freedesktop.org/show_bug.cgi?id=11231 crash with swfdec 0.4.x but 0.5.1 does not, fixed perhaps.

On Thu, Jan 30, 2020 at 1:21 PM Tom Stellard via cfe-dev <cfe-dev at lists.llvm.org> wrote: > > On 10/24/2019 07:54 PM, James Y Knight via llvm-dev wrote: > > We held a round-table at the llvm dev conference about what other pieces of Github infrastructure we may want to use. This thread in particular is about switching to github issue tracking. Use of other parts of Github

Would it make sense to wait until 10.0.0 is released, in order to keep all the blockers in one place? On Thu, Jan 30, 2020 at 1:32 PM Tom Stellard via llvm-dev < llvm-dev at lists.llvm.org> wrote: > On 01/30/2020 10:24 AM, Aaron Ballman wrote: > > On Thu, Jan 30, 2020 at 1:21 PM Tom Stellard via cfe-dev > > <cfe-dev at lists.llvm.org> wrote: > >> >

Hi, On Thu, Jan 30, 2020 at 10:21 AM Tom Stellard via cfe-dev < cfe-dev at lists.llvm.org> wrote: > On 10/24/2019 07:54 PM, James Y Knight via llvm-dev wrote: > > We held a round-table at the llvm dev conference about what other pieces > of Github infrastructure we may want to use. This thread in particular is > about switching to github issue tracking. Use of other parts

On Tue, 2020-08-25 at 14:12 -0400, Andrew Walker via samba wrote: > On Tue, Aug 25, 2020 at 1:17 PM James B. Byrne via samba < > samba at lists.samba.org> wrote: > > > > > > > On Mon, August 24, 2020 22:19, Andrew Bartlett wrote: > > > > > > > > A bit of an aside, but it would be incredibly awesome if the > > > FreeBSD >

On Wed, Feb 18, 2015 at 11:53 AM, Renato Golin <renato.golin at linaro.org> wrote: > On 18 February 2015 at 16:39, Jack Howarth > <howarth.mailing.lists at gmail.com> wrote: >> This still all begs the question of what exact metrics exist for the >> Q/A of llvm releases? IMHO, the bad PR from shoving out compiler >> releases with severe performance regressions in

Hi all, Now that it looks like we have some kind of process to manage tickets, I need people to help me with that process. There are currently something like 117 open tickets, and there are about 6 different dimensions on which these tickets can be categorized (e.g., complexity, triage stage -- all the report times listed on the Reports page). My plan is to work my fingers raw going