I agree, we should wait post 1.12 release to discuss this. at first, i wanted to wait for 1.12 release before talking about that, but todays discussion let me at least disappointed.
for the windows specific issue, absolutely no build env is needed because one PR targets the installer, the other one targets the default skin. You just need a windows machine to test. or at least discuss about the consequences of the change I propose. but, yes, more windows compiling env would be better ;) sb Le 22/07/2015 19:47, Be a écrit : > I agree. I think we should discuss these issues in detail after 1.12 is > released. For now, let's focus on getting those active PRs merged and > the manual. > > The long review time for Windows-specific issues is a problem. For me, > the issue is how much of a hassle it is to compile on Windows. I'd be > happy to borrow a computer with Windows for testing if that didn't > require installing a bunch of stuff to compile an unmerged pull request. > > On 07/22/2015 12:27 PM, Sébastien BLAISOT wrote: >> Hi, >> >> I strongly disagree with you. We have a wonderfull new feature with >> resizable skins and this new feature is ruined by our windows installer >> because if you install 1.12 on top of 1.11, you get the old skins :( >> Upgrade is not rare. We already discussed about that, I proposed a PR >> which is waiting review since 1+ month. Saying today that this is not a >> blocker don't correct the real problem : nobody seems to care about >> windows users. This is relatively easy to merge, we must improve 1.12 >> quality including this PR. >> >> In my opinion, the problems of the mixxx project aren't marketing or >> software quality, but two others : >> >> - The lack of release management process. We need to know when are the >> new functionnality merge windows, when we are in feature freeze, what >> and how we should consider blockers, and so on. and we need someone / a >> team that dispatch remaining work to achieve release with a clearly >> stated date or quality and focus every developpers on correcting >> remaining bugs when we are about to release (for example avoid wasting >> time talking about coding style during beta cycle). With a release >> managemen process, the goal won't shift, or only in a controlled way. >> >> - The lack of decision process. This project is only driven by strong >> consensus. When we don't have an overall agreement, nothing is done. it >> is normal, in real life, that different people have different opinions. >> We need a way to choose between different opinions. Either with a strong >> project leader, or with a published process (like voting for example). >> This should be published. >> >> --- >> Sébastien Blaisot ------------------------------------------------------------------------------ _______________________________________________ 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
