From: Anthony Green <green@moxielogic.com>
To: libffi-discuss@sourceware.org
Subject: libffi 3.3 release candidate 0
Date: Mon, 02 Apr 2018 12:54:00 -0000 [thread overview]
Message-ID: <CACxje595NQ2B04MA2kDd43E3w+E566miNvtX5mCaW5yBhquSBg@mail.gmail.com> (raw)
libffi 3.3 release candidate 0 is available for testing...
https://github.com/libffi/libffi/releases/download/v3.3-rc0/libffi-3.3-rc0.tar.gz
https://github.com/libffi/libffi/releases/tag/v3.3-rc0
I'm still aiming for a final release before the end of May. The purpose of
the release candidate is to test the packaging (make sure the release
tarball is complete) and collect initial test results for platforms not
included in the regular travis and appveyor CI systems.
Speaking of CI systems, any additional CI integrations or test
configurations (gcc on windows? running the tests on macos? etc) would be
particularly welcome. And, along those lines, I'd like to give special
thanks to github user @fwg for fixing the appveyor msvc CI testing
yesterday.
AG
next reply other threads:[~2018-04-02 12:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-02 12:54 Anthony Green [this message]
2018-04-04 21:05 ` Matthias Klose
2018-04-07 23:25 ` Anthony Green
2018-05-02 9:18 ` Alan Modra
2018-10-17 13:50 ` Matthias Klose
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CACxje595NQ2B04MA2kDd43E3w+E566miNvtX5mCaW5yBhquSBg@mail.gmail.com \
--to=green@moxielogic.com \
--cc=libffi-discuss@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).