There have been quite a few changes merged into the 1.7.x branch. How
about nuking this tarball, and rolling a new one? We *know* this
tarball isn't what we'd like to deliver to users, so why should we
bother posting it?
On Wed, Jul 13, 2011 at 16:29, Hyrum K Wright <hyrum_at_hyrumwright.org> wrote:
> Our first prerelease from the 1.7.x branch is now up for testing and
> signing: 1.7.0-beta1. The magic revision is r1146221 (but a known bug
> in the release scripts doesn't include that rev in the header file).
> You can find the tarballs here:
> There aren't any known release-blocking issues, but this is still a
> beta release. As you may expect, these prereleases are intended for
> intrepid users and testers only. Aside from the aforementioned
> revision number issue, the new release scripts appear to be behaving
> themselves, though any reports to the contrary would be of great
> I'd like to get a complete set of 3 *nix and 3 Windows signatures for
> this release. Barring any catastrophes, this will be the only beta,
> and we'll start the RC train in a week or two.
> Please send sigs here:
Received on 2011-07-17 11:21:15 CEST