From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/3728 Path: news.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Preparing to release 0.9.12 Date: Wed, 24 Jul 2013 16:02:21 -0400 Message-ID: <20130724200221.GA4256@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1374696155 12928 80.91.229.3 (24 Jul 2013 20:02:35 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 24 Jul 2013 20:02:35 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-3732-gllmg-musl=m.gmane.org@lists.openwall.com Wed Jul 24 22:02:35 2013 Return-path: Envelope-to: gllmg-musl@plane.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1V25Gc-0001JC-W8 for gllmg-musl@plane.gmane.org; Wed, 24 Jul 2013 22:02:35 +0200 Original-Received: (qmail 29859 invoked by uid 550); 24 Jul 2013 20:02:34 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 29839 invoked from network); 24 Jul 2013 20:02:34 -0000 Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Xref: news.gmane.org gmane.linux.lib.musl.general:3728 Archived-At: Hi everyone, The list of changes since 0.9.11 has grown quite large, and although we haven't met some of the roadmap goals for 0.9.12, others that were marked for 0.9.13 have already been finished. So I think it's reasonable to aim to release very soon now. There are still a few pending items I'd like to get committed before the release: - orc's getaddrinfo fix for AF_UNSPEC with NULL hostname - Andre's ARM memcpy optimizations - New crt1.c code for adding PIE support for more archs - MAYBE the symlink direction issue... Otherwise, between now and release I want to focus on detecting any regressions. I don't expect any functional regressions, but it's possible that the header refactoring broke some fragile, incorrect applications. Reportedly sabotage needed 3 extra patches to work around broken programs using __uint64_t and similar. Feedback from testing with current git (especially current git's headers) would be very helpful. Rich