RFC: time for a new mingwrt/w32api release?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Guys,

It's been a long time since we last released an update for this pair
of packages.  I'd like to prepare a new combined release, preferably
with synchronized version numbers, but given the problems inherent in
the last combined release, (v4.0), I think that any new release should
be derived from the current "legacy" branch, and should skip
immediately to a synchronized version number of 5.0.

To prepare for this, I'm considering:

1) Rename the existing "5.0-dev" branch as "5.0-deferred".
2) Create a new "5.0-dev" branch, based on the tip of "legacy".
3) Implement an integrated build infrastructure, preserving the
   existing separate package configuration, but building both
   together, with enforced version number synchronization.
4) Create an early 5.0 release, substantially unchanged from
   the current "legacy" tip, (possibly with a few new features
   which are already "good to go").

Any thoughts?  Objections?

- -- 
Regards,
Keith.

Public key available from keys.gnupg.net
Key fingerprint: C19E C018 1547 DE50 E1D4 8F53 C0AD 36C6 347E 5A3F
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)

iQIcBAEBAgAGBQJXNPhiAAoJEMCtNsY0flo/eJAP/3TmB73IRUMbuGf7jzMDzrxG
m50njM3TNHx0lv9mFsLZBSdlc4xPl2MXQt60wk6vp3bH3Sug0fsooykCh6RHdOWb
N9nrR+W/HuoIT4tATrByqP5bHMIuGX0iwMN21rvecSyAtBiG8SZV57Z00+7kmW7/
upY37sl5tFE/m5fzjdiRdvB6ieK1afeIrtI60LkA86JsuuuRqgkSHjnz34HLzlPX
Ix3fXU3W6feX7FxDRN2SEySUNDXdoq7EubhFrv3hZGwXs+VjWSt08uFfJMvy5/Hm
iYmDMJo0KLmy7WC5p3LT8/BvQSV6h8nOImWdkBD56hR7eL7y6Vi4g+i32BKuVtog
uJs5GHcOfxpg3kFELJXbuYLKkI60+WztZtBB/Ou4CMgSD/quEJXaqzbkiCaEZLsA
p0UI7lCmC1qkhR0r8lw8IdTDQZVH5nz++XSe2B+4xz4QiaarrAUuhvvebFyFDD9u
y/GzEH135/Tl2XbO/54ige0D2IZreywW9+j6L5Xggab7HIsYYXNBmn2dGYvFxar7
dZHtYWUhLcokSdOPmWTaDnZRdnPa1WOqWk9O9TxDeuBOdbSHTN4regr/b7OIn6pG
7EnwafSwNShQ40fC3Yf2TQ7j609H+Wn3Cx4j/0qI8+pEBgcvQYiVfSzXdcWsqY4X
DLZXNKndwiO6VE2vGYxV
=+8jD
-----END PGP SIGNATURE-----

------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j