Hi Markus, I am also quite unhappy, that we missed a suitable release date as we have original planed "short after 2.0". Later in September, we had also a very stable alpha version that was suitable for merge.
Now we are in a middle of a giant feature creep, polishing skins and controller interface. It would feel bad to release Mixxx with this halve finished. The involved contributors are very productive and hard working, so I think we are ready for release soon. My tasks are already done and pending as PR Mandatory: HiDPI Skin Scaling https://github.com/mixxxdj/mixxx/pull/1204 Hint rounding https://github.com/mixxxdj/mixxx/pull/1223 Optional: LV2 support: https://github.com/mixxxdj/mixxx/tree/lv2_support2 Optional network clock reference https://github.com/mixxxdj/mixxx/pull/894 Auto dj crates improvements https://github.com/mixxxdj/mixxx/pull/1214 Show native separators in user visible strings (GUI) https://github.com/mixxxdj/mixxx/pull/1215 If I find time, I would also look at the DB rename detection. I am afraid it is broken, because I have a lot of missing tracks in my library. What else is mandatory for the release? Kind regards, Daniel Maybe they can give an Am 23.03.2017 um 21:34 schrieb Markus Klösges: >> We have accumulated a rather large backlog of pull requests that are > awaiting review and testing. > > IMHO it would also be nice to have some more info on release schedules > or plans, what could be merged and what is laying around for next alpha. > What to focus on, where help is wanted. Maybe GitHub tags could be used > for marking 'please test', 'next alpha', ...? In combination with some > more communication about planned releases, that could probably help > focusing the work. > What do you think? > > Am 23. März 2017 16:56:03 MEZ schrieb Be <b...@gmx.com>: > > We have accumulated a rather large backlog of pull requests that are > awaiting review and testing. I wrote a new wiki page and put it on the > front page of the wiki to help users get involved with testing: > http://mixxx.org/wiki/doku.php/testing > > To get more testers, it would be helpful to make the builds Travis makes > available for download. AppVeyor already does this and keeps the builds > on the AppVeyor site. Could we host those on Travis or have the Travis > VMs send the builds to our build server for hosting? > > ------------------------------------------------------------------------ > > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org <http://Slashdot.org>! > http://sdm.link/slashdot > ------------------------------------------------------------------------ > > 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 > > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > > > _______________________________________________ > 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 > ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ 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
