Moving to gitlab for issues while sticking to github for code would come
with all the annoyances of having to switch systems without any of the
benefits of having code and issues in the same place..
On Thu, Nov 16, 2017 at 5:41 PM, Sean M. Pappalardo - D.J. Pegasus <
spappala...@mixxx.org> wrote:
I have some time after next week to do some work on the manual, is there a
list of things that need to be updated/written?
On Thu, Nov 16, 2017 at 8:23 AM, Daniel Schürmann
wrote:
> Hi Mixxx developers,
>
> I am glad to announce a release schedule for Mixxx. We have decided
Regarding disadvantages of GitHub
*Doesn't explicitly support rich states other than just open/closed*
If for progress tracking - milestones are great for this.
*Not possible to link related issues*
Maybe not in the same way, but you can links commits to issues in a really
nice way
*Not
Just comment on the PR on github. Testing is always good!
On Thu, Jul 6, 2017 at 4:19 PM, Waylon Robertson
wrote:
> Okay, i find myself playing with PR's, and testing mixxx live. I was
> wondering, how can i as a developer, capitalise on this, by testing
> PR's and
I like the current behavior as well.
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Get Mixxx,
My mapping PR for the Mixtrack Pro 3 is ready to go and works well with the
current master version (tested live several times now)
https://github.com/mixxxdj/mixxx/pull/1180
On Thu, Mar 23, 2017 at 3:01 PM, Daniel Schürmann
wrote:
> Hi Markus,
>
> I am also quite unhappy,
ongside the old system.
>
> 2. I agree that would be nice, but that is a separate issue. Owen
> started a proposal and proof of concept for that a while ago, but I
> don't think there has been progress on it lately:
> http://mixxx.org/wiki/doku.php/controller_preferences
>
> On 0
Having to also understand the XML mapping structure and how it worked on
top of learning Mixxx internals was a big sticking point for me. This
proposal would make it significantly easier for anyone with Javascript
background to dig right in.
Two things I'd like to bring up:
1. backwards