We have already announced Mixxx 2.1 for Q1 2006: http://mixxxblog.blogspot.de/
I would like to reserve Versions 2.0.x for urgent fixes on top of the 1.12 branch. This gives us the freedom to release a quick fix whenever required, without a beta phase. 2016-01-07 15:04 GMT+01:00 Be <b...@gmx.com>: > What new features are already in the master branch? If it is mostly bug > fixes with few new features, then I think it might be more appropriate to > call the next release 2.0.1. > > On 01/07/2016 03:31 AM, Daniel Schürmann wrote: > >> Hi, >> >> here my view:only bug >> >> * Lets skip 2.0.1 >> * Cut out a 2.1 branch now, it is already pretty mature and includes a >> lot of bugfixes and improvements. >> * Start the 2.1 beat phase now and apply only bugfixes to it. We do not >> need more features. >> * Announce a 2.1 release for KW 11 >> * Do all planed and pending work for new features in master towards a >> 2.2. Release scheduled KW 47. >> * Schedule the Release KW 47 and a 2.2 beta KW 36 (After GSOC 2016) >> * If we have something urgent, that is not ready before KW 11, we can >> release a 2.1.1 once it is ready. >> >> KW = Week of the year 201 >> >> Will this work for all? Other ideas? >> >> >> Kind regards, >> >> Daniel. >> >> >> >> >> >> 2016-01-07 7:11 GMT+01:00 Be <b...@gmx.com <mailto:b...@gmx.com>>: >> >> What are the plans for development going forward? How can we keep >> Mixxx >> consistently releasing updates without huge gaps between releases? >> Will >> there be a release of 2.0.1 before 2.1? If so, when, and what will >> this >> release bring? What is the release date target for 2.1? What can >> reasonably get done in that time? >> >> IMO the focus of 2.1 should be tying up the loose ends of 2.0. In >> particular, inconsistency between the skins should be minimized, >> especially for effects. To be clear, I don't think every skin should >> be >> the same, but they should all provide access to all of Mixxx's >> features. >> >> Who plans to work on what for 2.1? Let's set deadlines for ourselves. >> I >> aim to have at minimum a proof of concept for a JS library by the end >> of >> January. >> >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> Get Mixxx, the #1 Free MP3 DJ Mixing software Today >> http://mixxx.org >> >> >> Mixxx-devel mailing list >> Mixxx-devel@lists.sourceforge.net >> <mailto: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
