wine patches the black hole of code?

Posted by twickline on Jul 27, 2009 12:00 PM EDT
wine-reviews; By Tom Wickline
Mail this story
Print this story

On Monday, I took part in the first Wine Bug Day (one of hopefully many). It was a great success, I managed to rope in some support from some friends specifically Sean and Yorik both of whom are Wine users, not Wine developers (yet!).

And it wasn't just us, there was of course Scott Ritchie who organized the thing, but also several users popped up in #winehackers asking for others to change the status of their bugs. It was all quite exciting in a weird kind of way.

On Monday, I took part in the first Wine Bug Day (one of hopefully many). It was a great success, I managed to rope in some support from some friends specifically Sean and Yorik both of whom are Wine users, not Wine developers (yet!).

And it wasn't just us, there was of course Scott Ritchie who organized the thing, but also several users popped up in #winehackers asking for others to change the status of their bugs. It was all quite exciting in a weird kind of way.

Patches rarely receive feedback - positive or negative - on the wine-patches list
Patches that are rejected aren't labelled as such, or publicly given a reason for why they were.
Hundreds of patches don't get in, that just need a tweak or two, that would REALLY improve the wine experience.
These failed patches can't easily be seen by anyone unless they know exactly what to Google for.

Full Story

  Nav
» Read more about: Story Type: Editorial; Groups: Community

« Return to the newswire homepage

Subject Topic Starter Replies Views Last Post
Sounds like this guy is onto something softwarejanitor 0 904 Jul 27, 2009 12:28 PM

You cannot post until you login.