If there are any skin artists listening, please don't wait for the beta release to start working :).
I don't have a good sense of where the EQ rack is at, but I saw the kill buttons go through so it does feel like we're almost there. Is there any chance of having it be switchable from the old style to the new style, or does that miss the point entirely? Why GUI elements does it need? I thought it would just plug in to existing skins (and crazy eqs with filters != 3 would be excluded from being used for main EQs to keep things sane). While I agree that segfaults and party stoppers are final release blockers, I don't actually think they should be beta blockers. It's a common practice to release a beta and say "here are the known issues" as long as it's a short and well-defined list. It sounds like we're pretty close. I would strongly urge everyone to focus on their own personal blocker list, even if there are eager new developers with PRs they want reviewed. We don't have a big team, and right now I think it's better to tell people "I understand you've worked hard on this, but right now I am working on XYZ to get mixxx released. Please be patient." On Fri, 2014-11-14 at 20:46 +0100, Daniel Schürmann wrote: > Hi Owen, > > the Deere skin is no blocker for me. I have got the feeling (or I hope) > that the skin artists are > waiting for the beta release. We can call the release: Interface fixes, > Ready for skinning. > > The EQ Rack is almost merged, it feels wired to release Mixxx in this > state. > I hope I fix the remaining known issues today. > Jus has done a GUI / concept review a second (code) review would be > nice, any volunteers? > > A blocker for me are the memory leaks an the re-producible segfaults and > other known party stoppers. > I can have a look on the problems on Linux once EQ Rack is merged. > Who will have a look on windows? > > A personal blocker for me is the missing non-chopped album art view for > small screens. > 100 pixel width is simply to much. An I can't deal with the upper > snipped :-/ > @Max, @Cardinot You have offered to work on it after merge. Do you make > progress > or should I jump in? > > Kind regards, > > Daniel > > > > > > Am 14.11.2014 um 15:21 schrieb Owen Williams: > > We've been making really good progress recently (hurray covers!), and I > > want to get a feel for what other people think about the current status > > of the build as well as put some pressure behind a beta release. To > > that end, at some regular interval, maybe every two weeks, I'll send an > > email to the list asking "Why not now?" The idea being, the devs should > > provide a list of the fixes/features/work that they think are preventing > > a beta release. > > > > For myself, I'd say my only major blocker is that the Deere skin needs > > to be cleaned up. Max and I had talked about some things, and he > > mentioned some manual work that needs to be done. I need to flesh out > > the bits about master sync, the midi wizard, and the new skin system for > > example. > > > > The problem with this tactic is that I've been sitting around waiting > > for someone to pick up the Deere skin work. That creates a conflict > > between me thinking the skin needs fixing for the release, but nobody is > > doing it. So my controversial addition to this plan is: if you think > > something is a blocker, you do the work on it :). If you think someone > > else's PR needs to get finished, I think it's time to just pick it up > > and finish it. So this weekend I will start poking at Deere, removing > > all the crazy background colors and cleaning it up. > > > > (There has been some hesitation releasing a beta because a beta should > > be releasable as a proper major version if it goes well. I actually > > disagree, since that's what I'd call a "release candidate." But if we > > want to call the next release an alpha2 that's ok with me.) > > > > So like I said, here are my blockers: > > > > * Deere skin work > > * Manual updates > > > > So, why not now? > > > > > > ------------------------------------------------------------------------------ > > Comprehensive Server Monitoring with Site24x7. > > Monitor 10 servers for $9/Month. > > Get alerted through email, SMS, voice calls or mobile push notifications. > > Take corrective actions from your mobile device. > > http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk > > _______________________________________________ > > Get Mixxx, the #1 Free MP3 DJ Mixing software Today > > http://mixxx.org > > > > > > Mixxx-devel mailing list > > Mixxx-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/mixxx-devel > > > ------------------------------------------------------------------------------ > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push notifications. > Take corrective actions from your mobile device. > http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk > _______________________________________________ > Get Mixxx, the #1 Free MP3 DJ Mixing software Today > http://mixxx.org > > > Mixxx-devel mailing list > Mixxx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mixxx-devel > > ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk _______________________________________________ Get Mixxx, the #1 Free MP3 DJ Mixing software Today http://mixxx.org Mixxx-devel mailing list Mixxx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mixxx-devel
