3/31/2023 0 Comments Mixxx 2.0.0![]() ![]() > aim to have at minimum a proof of concept for a JS library by the > Who plans to work on what for 2.1? Let's set deadlines for > the same, but they should all provide access to all of Mixxx's > there be a release of 2.0.1 before 2.1? If so, when, and what will > consistently releasing updates without huge gaps between releases? > What are the plans for development going forward? How can we keep > * If we have something urgent, that is not ready before KW 11, we can > * Do all planed and pending work for new features in master towards a > * Start the 2.1 beat phase now and apply only bugfixes to it. ![]() > * Cut out a 2.1 branch now, it is already pretty mature and includes a Is going to be release in sametime window? When release is made then have merge window and branch new stable that Should we make some Gnome/KDE base timebased release system or Kernel > * If we have something urgent, that is not ready before KW 11, we can release a 2.1.1 once it is ready. ![]() > * Schedule the Release KW 47 and a 2.2 beta KW 36 (After GSOC 2016) > * Announce a 2.1 release for KW 11 * Do all planed and pending work for new features in master towards a 2.2. * Start the 2.1 beat phase now and apply only bugfixes to it. > * 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. (I'm waiting for the first manual wix package on the build server to PR744 first, install wix on build server and integrate wix with scons I would like to have the new installer for 2.1, but we need to merge > Get Mixxx, the #1 Free MP3 DJ Mixing software Today > aim to have at minimum a proof of concept for a JS library by the end of > Who plans to work on what for 2.1? Let's set deadlines for ourselves. > the same, but they should all provide access to all of Mixxx's features. To be clear, I don't think every skin should be > particular, inconsistency between the skins should be minimized, > IMO the focus of 2.1 should be tying up the loose ends of 2.0. > release bring? What is the release date target for 2.1? What can > there be a release of 2.0.1 before 2.1? If so, when, and what will this > consistently releasing updates without huge gaps between releases? Will > What are the plans for development going forward? How can we keep Mixxx * If we have something urgent, that is not ready before KW 11, we can * Schedule the Release KW 47 and a 2.2 beta KW 36 (After GSOC 2016) * Do all planed and pending work for new features in master towards a 2.2. Src/musicbrainz/chromaprinter.* Cut out a 2.1 branch now, it is already pretty mature and includes a lot Src/musicbrainz/chromaprinter.cpp: In member function Ă¢QString ChromaPrinter::calcFingerPrint(const SoundSourcePointer
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |