14.12.2013 0:24, Sean McNamara пишет:
> Hi,
>
Hi Sean,
>
> 1. For now, you make a "tested" build based on git master, which you
> have personally evaluated and find that it is mostly correct, except for
> any platform-independent bugs that are already known but not yet fixed.
> This basically con
14.12.2013 0:10, Max Kellermann пишет:
>
> I'm all for fixing bugs in the stable branch, but if your idea of (2)
> is to backport the master code, then this is not my idea of a stable
> branch, and we're better off with (1).
>
> However my preference would be (3): fix only the regressions that made
Hi,
As a potential user (:)) of the Windows builds, I would like to propose
that:
1. For now, you make a "tested" build based on git master, which you have
personally evaluated and find that it is mostly correct, except for any
platform-independent bugs that are already known but not yet fixed. T
On 2013/12/13 19:08, Denis Krjuchkov wrote:
> 1) Provide binaries for ongoing master branch. Since this is a
> development branch it might be less stable, however again from my
> experience it works well.
>
> 2) Backport important changes from master to 0.18.x and keep updating it
> as 0.18.x
Hello list,
some months ago I proposed my self as a Windows binaries maintainer.
I'm still committed to this task.
However 0.18.x branch is unusable on Windows due to GLib event loop
implementation oddities. In short: it does not work.
Current MPD trunk (v0.19.x) supports native Windows event l
