similar to: Still need help with ticket triage

I''m still thinking about how my puppet deployment will go. Right now, I''m thinking each of my machines will have their network interfaces defined/configured by puppet. But, I''d like to generate my zone files and dhcpd.conf from this data as well. How do people generally do this? I expect I''ll end up generating the nodes.pp files from some database, but

Hello I was wondering if 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

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

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)

Wine is approaching the 0.9 release, and it's time to start fixing all the lingering bug reports in Wine's bug database. You can help the Wine developers do this even if you're not a developer yourself! All you have to do is spend an hour trying to reproduce a bug that somebody else filed. If you're interested, please go to http://kegel.com/wine/qa for step-by-step instructions.

Hi, Yesterday, I’ve landed a description for how reported bugs should be flowing through the various stages of a bug’s life (triage, fixing, closing, …) at http://llvm.org/docs/BugLifeCycle.html. Thanks for the many many people who provided ideas and feedback for this! With there now being a description of what is expected during bug triaging

Hi Zach, Thanks for putting the data in a spreadsheet - that’s easier to navigate. 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

Hi Zach, Thanks for elaborating. I like your proposal. I agree it still groups per area of expertise. And it makes the set of components we have easier to manage. Before making changes though I hope to hear opinions from others on this. What do others think? Thanks, Kristof On 9 Nov 2018, at 18:05, Zachary Turner <zturner at google.com<mailto:zturner at google.com>> wrote: To

I had considered a libraries/Backends:Other as well that would be separate from libraries/Other On Fri, Nov 9, 2018 at 11:20 AM Derek Schuff <dschuff at google.com> wrote: > I wonder if backends are a special case to the heuristic of "let's not > make a bug component for code components that are too small". LLVM is > factored to cleanly separate backend code, to the

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

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.

I''m fairly new to the Ruby world, particularly WxRuby, so please forgive me if this is ground that''s been covered in the past. I''m trying to load a frame from an XRC file (created using DialogBlocks), and I''m having trouble getting an instance of the Gauge object using the Wx::Window.find_window_by_xxx methods. I''m trying this on Windows XP,

Hi All, For quite some time I've used raid 1 as a means of providing a rollback mechanism for an upgrade (which I learned from others long ago). So essentially, before an upgrade you split the mirrors and upgrade one side or the other. If your upgrade goes well you sync one way, if your upgrade does not you sync the other (much hand waving and chanting going on, as its more complicated than

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

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 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

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

To a user, samba_dlz just doesn't work correctly with bind. There are two obvious options a) bind is broken somehow and unloads all modules when reloading b) samba_dlz is somehow broken in the way that it interfaces with bind, perhaps it misinterprets the signal to 'reload' when it receives it from bind. As a user, i have no way of knowing which is it is, all that I know is that

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: > >> >