Re: [Mixxx-devel] 2.1 beta release logistics

2017-12-24 Thread Be
I cannot reproduce the failing test locally using the latest 2.1 branch. On 12/24/2017 10:46 AM, Be wrote: Windows and macOS are still failing with the same errors with the current code. Ubuntu is failing because of a test I thought I already fixed, but I'll look into that again... On

Re: [Mixxx-devel] 2.1 beta release logistics

2017-12-24 Thread Be
Err, whoops, I copy and pasted the wrong link. The beta announcement is live on the main website: https://mixxx.org/download/ On 12/24/2017 01:53 PM, Be wrote: I got in touch with Garth who got me access to the web server and deployment instructions from RJ. The beta announcement is deployed

Re: [Mixxx-devel] 2.1 beta release logistics

2017-12-24 Thread Be
I got in touch with Garth who got me access to the web server and deployment instructions from RJ. The beta announcement is deployed on http://staging.mixxx.org/download/ . We still don't have builds for the 2.1 branch so it just has instructions for downloading the source from GitHub. I still

Re: [Mixxx-devel] 2.1 beta release logistics

2017-12-22 Thread Be
So is this happening today...? On 12/22/2017 01:44 PM, Be wrote: Things that must be done for the 2.1 beta release:   * Merge the master Git branch to the 2.1 branch   * Create a folder on http://downloads.mixxx.org/ to upload 2.1 beta builds   * Check that Jenkins is building the 2.1

Re: [Mixxx-devel] 2.1 beta release logistics

2017-12-22 Thread Be
I would have already been doing that if I could. On 12/22/2017 02:45 PM, Sébastien BLAISOT wrote: ok, sorry. I understand now. on the other hand, why trying to correct build error of 1-year-old code ? wouldn't it be better to merge first, then try to build ? sb Le 22/12/2017 à 21:35, Be

Re: [Mixxx-devel] 2.1 beta release logistics

2017-12-22 Thread Sébastien BLAISOT
ok, sorry. I understand now. on the other hand, why trying to correct build error of 1-year-old code ? wouldn't it be better to merge first, then try to build ? sb Le 22/12/2017 à 21:35, Be a écrit : That's the Jenkins build for the master branch, not 2.1. The 2.1 branch has not had

Re: [Mixxx-devel] 2.1 beta release logistics

2017-12-22 Thread Be
That's the Jenkins build for the master branch, not 2.1. The 2.1 branch has not had updates from master in almost a year. On 12/22/2017 02:33 PM, Sébastien BLAISOT wrote: this seems to be related to the jenkins error to me:

Re: [Mixxx-devel] 2.1 beta release logistics

2017-12-22 Thread Be
That is unrelated to the Jenkins error. I already opened a PR to fix the AppVeyor error: https://github.com/mixxxdj/mixxx/pull/1437 On 12/22/2017 02:27 PM, Sébastien BLAISOT wrote: windows error is here: [00:09:48] [CXX] src\engine\ratecontrol.cpp [00:09:48] ratecontrol.cpp [00:09:49]

Re: [Mixxx-devel] 2.1 beta release logistics

2017-12-22 Thread Sébastien BLAISOT
windows error is here: [00:09:48] [CXX] src\engine\ratecontrol.cpp [00:09:48] ratecontrol.cpp [00:09:49] src\engine\ratecontrol.cpp(26): error C3431: 'RampMode': a scoped enumeration cannot be redeclared as an unscoped enumeration [00:09:49] scons: *** [win64_build\engine\ratecontrol.obj]

Re: [Mixxx-devel] 2.1 beta release logistics

2017-12-22 Thread Be
2.1 branch build is failing on Jenkins for Windows and macOS. Windows build shows: Checking for C library vamp-sdk... no WE ARE IN: E:\Jenkins\workspace\2.1-release\architecture\i386\platform\windows\win32_build Building 2.1 - rev. 6261 scons: warning: Two different environments were

[Mixxx-devel] 2.1 beta release logistics

2017-12-22 Thread Be
Things that must be done for the 2.1 beta release: * Merge the master Git branch to the 2.1 branch * Create a folder on http://downloads.mixxx.org/ to upload 2.1 beta builds * Check that Jenkins is building the 2.1 branch and uploading builds to downloads.mixxx.org * Post the release