On 2013.06.19 15:29, Hans de Goede wrote:
> So as promised I've been working on this today, but I ended up spending
> most of my time on sorting through a number of the open issues
> (...)
> The open issue count is down from 54 to 44 now
Good job. :)
I just tested cygwin/WDK/MinGW-Clang/VS2012 co
Hi,
On 06/11/2013 12:10 PM, Hans de Goede wrote:
> Hi,
>
> I think it would be good to tag current master as 1.0.16-rc1, spin
> tarbals, etc.
So as promised I've been working on this today, but I ended up spending
most of my time on sorting through a number of the open issues in:
https://github.c
Hi,
On 06/11/2013 12:10 PM, Hans de Goede wrote:
> Hi,
>
> I think it would be good to tag current master as 1.0.16-rc1, spin
> tarbals, etc.
>
> I'm willing to the work for this (*), with the exception of providing
> windows binaries.
So, with the hotplug thread issue Xiaofan found fixed, I thin
Hi,
On 06/12/2013 01:45 AM, Pete Batard wrote:
> On 2013.06.11 11:10, Hans de Goede wrote:
>> I think it would be good to tag current master as 1.0.16-rc1, spin
>> tarbals, etc.
>
> I'd prefer if we don't tag the RC-1 until next Monday, on account that:
> - I'd like to keep at least a little dista
On 2013.06.11 11:10, Hans de Goede wrote:
> I think it would be good to tag current master as 1.0.16-rc1, spin
> tarbals, etc.
I'd prefer if we don't tag the RC-1 until next Monday, on account that:
- I'd like to keep at least a little distance between 2 major events,
such as the announcement of
Hi,
I think it would be good to tag current master as 1.0.16-rc1, spin
tarbals, etc.
I'm willing to the work for this (*), with the exception of providing
windows binaries.
Pete, I believe that you've a checklist for the release process somewhere ?
Also I guess we should update the README with
