From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/3957 Path: news.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: Preparing for 0.9.13 release Date: Sun, 25 Aug 2013 02:49:55 -0400 Message-ID: <20130825064955.GU20515@brightrain.aerifal.cx> References: <20130823180119.GA11418@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 1377413405 32296 80.91.229.3 (25 Aug 2013 06:50:05 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 25 Aug 2013 06:50:05 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-3961-gllmg-musl=m.gmane.org@lists.openwall.com Sun Aug 25 08:50:08 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 1VDU9I-0005Eg-5T for gllmg-musl@plane.gmane.org; Sun, 25 Aug 2013 08:50:08 +0200 Original-Received: (qmail 30160 invoked by uid 550); 25 Aug 2013 06:50:07 -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 30152 invoked from network); 25 Aug 2013 06:50:07 -0000 Content-Disposition: inline In-Reply-To: <20130823180119.GA11418@brightrain.aerifal.cx> User-Agent: Mutt/1.5.21 (2010-09-15) Xref: news.gmane.org gmane.linux.lib.musl.general:3957 Archived-At: On Fri, Aug 23, 2013 at 02:01:19PM -0400, Rich Felker wrote: > Hi everyone, > > The major goals for 0.9.13 have been met and I'm hoping to prepare a > release sometime in the next few days. There are still a few issues I > want to address though, which I'm looking for some volunteers to help > with: > > 1. Tracking down orc's problem with resolver (see the thread with > subject line "dn_expand() confuses postfix"). I think this is fixed now. (commit 7211551e9ff7c8c9d1491856088cf832f2722bd6) > 2. Writing tests for strftime and wcsftime (to catch any regressions > from the recent field width additions or old bugs). I've caught some issues myself, but haven't actually done any heavy testing. For most format specifiers, I think just basic sanity checks would suffice. Anything that involves computation (like week-based year stuff) would also benefit from boundary value checks. For time zone related things, testing inputs created by both localtime and gmtime, and with different types of time zone settings (GMT, POSIX with and without DST, old and new zoneinfo) would be useful. Rich