Re: RFC: time for a new mingwrt/w32api release?

Em 05-12-2016 18:40, Keith Marshall wrote:
> 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.

OK.

> 
> 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".

Anyone who is tracking locally the old "5.0-dev" branch, and tries to
pull, will get conflicts, as git tries to merge the two branches. On the
other hand, there is a good chance that the number of affected people,
actively tracking the "5.0-dev" branch, is actually zero.

> 3) Implement an integrated build infrastructure, preserving the
>    existing separate package configuration, but building both
>    together, with enforced version number synchronization.

Interesting. Will there be only one source tarball? Will "make install"
create a mix of the two packages in $prefix/include and $prefix/lib,
which the packager will have to untangle later?

> 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").

Sure.

Regards,
Cesar

------------------------------------------------------------------------------
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