Hi guys, A bunch were able to put in some serious Mixxx time this weekend and we're very close to declaring development finished and releasing Mixxx 1.8.0. If you have any lingering changes that absolutely can't wait for 1.9, please submit them by Tuesday. At this point, any changes to the engine or other error-prone code are going to have to wait.
For those of you who are on board for your first Mixxx release, we usually try to release when got the point where: 1) We're pretty sure we've fixed all the crasher bugs 2) The influx of new bugs has slowed, and we've caught up fixing the most important ones. (It's a balance between how much time we can put into Mixxx and polish.) We think 1.8.0 is ready, and it's going to be a huge improvement over 1.7.2 for our users. :) Over the next week, we still need to do the following: - Try to do some formalized quality assurance checking on 1.8.0 (for the first time): http://mixxx.org/wiki/doku.php/qa_procedure - Update the manual on the wiki. I'll roll it into a PDF and put it in bzr once we're happy with it. If the QA testing goes well, we can proceed with packaging maybe by next weekend. The new website's also done, and will go online when the new release goes live. Thanks guys! Albert ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Mixxx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mixxx-devel
