RFC: time for a new mingwrt/w32api release?
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?
Public key available from keys.gnupg.net
Key fingerprint: C19E C018 1547 DE50 E1D4 8F53 C0AD 36C6 347E 5A3F