glpk problems on cygwin

[soren at hauberg.org]

Quoting Jaroslav Hajek <highegg at gmail.com>:
> Can this wait till 3.0.3? 3.0.2 has already been made and tagged in
> the release archive, and a few people had made builds. Please note
> that I intend to cut down the intervals between minor releases; you
> can expect 3.0.3 until the end of September.
> But I think that only build failures or perhaps test segfaults are
> serious enough to unfreeze an already frozen release.
> Also, I currently follow the policy of waiting for changesets to be
> applied into development archive then transplant them; I'd like to
> avoid diverting from the development archive as much as possible. John
> has not, however, applied the patch yet, so that would mean another
> delay for 3.0.2.
>
> opinions?

I agree that you shouldn't unfreeze 3.0.2. That'll cause too much  
confusion. If this is really a big issue (IMHO it's not) then I guess  
you could do a 3.0.3 release containing this patch.

Søren