On Tue, Jun 2, 2015 at 4:40 PM, Daniel Schürmann <dasch...@mixxx.org> wrote:
> Hi RJ, > > > Someone recently gave me a Windows laptop so I'm going to setup a > Windows build environment to try and look at some of these. > > Thank you for looking at this. Would you mind to provide windows symbol > files from the build server as well? This way we are able to get > more infos directly from the effected systems. > Yea, PDB bundling is on my list as well. > > > Adding a 1.12.1 will likely cause more bugs in the wild than it fixes > and that's not what users will expect from a point release. > > The SS branch is in master since a while and I have a very good feeling > for the quality but we do not know. > On the other hand, if we add Qt 5 and c++11 refactoring and upcomming and > pending feature branches, > we will add a risk of an additional "ton" of bug and not the least a risk > of an other year delay. So if we want an > SS release soon we should not do this. > qt5 support has been in for nearly a year. The transition won't be too bad there. > It is OK for me to keep the 1.12 branch open for minor fixes towards a > possible 1.12.1 version without the SS changes. > > IMHO we need a separate branch for releasing the SS fixes. If it is called > 1.12.1 1.13 or 1.12.2 does not matters to me. > The only thing that matters is that we can put it in a alpha state now. > This will us give the time we need to lift it up to release state, without > blocking any other improvements for master. > We already have master builds and the nightly PPA for this purpose. > I think it will not be a problem to release a "1.13.0 SS only" independent > from a 1.12.1. > Is such a strategy OK to you? > Why would we cut a release branch for 1.13.0 when we haven't even released 1.12.0? There's a lot of overhead involved in doing a release. There is no compelling reason why SS-refactor needs to be in a release all of its own other than that you want it to be released ASAP. RJ > What do the others think? > > Kind regards, > > Daniel > > > > > > > > > Am 02.06.2015 um 21:29 schrieb RJ Ryan: > > > > On Sat, May 23, 2015 at 8:40 AM, Max Linke <max_li...@gmx.de> wrote: > >> >> >> On 05/20/2015 12:40 PM, Daniel Schürmann wrote: >> > Hi >> > >> > # Mixxx 1.12 beta # >> > >> > My Mixxx 1.12 beta experience on Linux is very good. I do not see any >> > issue that >> > justifies holding back the release any longer. >> > > I believe the blocking items are: > > * critical Windows bugs > * skin polish (Jus has an active Deere branch) > * website updates (I'm working on this) > * manual updates > > The skins are in kind of bad shape at the moment. They really need > polish to bring them to design bar that we set pretty high with 1.11.0. > > Someone recently gave me a Windows laptop so I'm going to setup a > Windows build environment to try and look at some of these. > > >> > >> > On the other hand Mixxx 1.12 beta still suffers 11 critical bugs. All of >> > them happen on windows only. >> > My overall test experiences running Mixxx on windows are also bad, do >> > others on the list share this experience? >> >> I have problems with the cover-art feature using the release builds that >> we distribute. But I haven't been able to debug this because I can't >> reproduce it in with my own builds. Do other people have problems with >> the covers? >> >> I haven't done much testing otherwise. >> >> > For me those issues actually block a release. >> > >> > Unfortunately there is no notable progress on these critical issues. >> > We need help! Is there anyone with a Windows build environment on the >> > list who can reproduce one of the critical bugs? >> > >> > >> > # New Soundsource API # >> > >> > The master branch, including the mp3 seek and click issues and floating >> > point samples has reached a stable state. >> > As discussed before it is planed to release a 1.12.1 or whatever >> > version, including these >> > important fixes. Since this will be a bugfix release, it should not >> > contain new features, >> > or other risky changes. >> > >> > We have also some pending pull request on Github, which may not fit to >> > such a 1.12.1 target. >> > So I think we should branch a 1.12.1 branch right now. >> > IMHO we can enter 1.12.1 beta stage after merging Uwes "SoundSource >> > Plugin API: Version 8" branch. >> > A release can be scheduled ~ two month after 1.12.0 to allow to include >> > add-hock fixes. >> > >> > > A 1.12.1 release is for fixing critical bugs that come up post-release > and it will be released out of the 1.12 branch. If the number of bugs we > hit right away after the SS-refactor merge is any indication there are tons > of bugs we haven't yet hit out in the wild. Adding a 1.12.1 will likely > cause more bugs in the wild than it fixes and that's not what users will > expect from a point release. > > I totally understand wanting to get master into a release ASAP though. > 1.13.0 will come soon after 1.12.0. It will probably be a clean-up / > stability improvements / refactoring release so it makes sense to include > the SS refactor there along with other changes (c++11 refactorings, Qt5 > support). > > It's fine to start merging the feature branches that are ready to master > -- they can be part of 1.13.0. > > > What do you think? >> > >> > Kind regards, >> > >> > Daniel >> > >> > >> > >> ------------------------------------------------------------------------------ >> > One dashboard for servers and applications across Physical-Virtual-Cloud >> > Widest out-of-the-box monitoring support with 50+ applications >> > Performance metrics, stats and reports that give you Actionable Insights >> > Deep dive visibility with transaction tracing using APM Insight. >> > http://ad.doubleclick.net/ddm/clk/290420510;117567292;y >> > >> > >> > >> > _______________________________________________ >> > 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 >> > >> >> >> ------------------------------------------------------------------------------ >> One dashboard for servers and applications across Physical-Virtual-Cloud >> Widest out-of-the-box monitoring support with 50+ applications >> Performance metrics, stats and reports that give you Actionable Insights >> Deep dive visibility with transaction tracing using APM Insight. >> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y >> _______________________________________________ >> 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 >> > > >
------------------------------------------------------------------------------
_______________________________________________ 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
