From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.52.177.71 with SMTP id co7csp43484vdc; Mon, 13 May 2013 16:23:06 -0700 (PDT) X-Received: by 10.60.37.7 with SMTP id u7mr4937022oej.120.1368487385980; Mon, 13 May 2013 16:23:05 -0700 (PDT) Return-Path: Received: from rubyforge.org ([50.56.192.79]) by mx.google.com with ESMTP id a3si17393269obt.25.2013.05.13.16.23.05 for ; Mon, 13 May 2013 16:23:05 -0700 (PDT) Received-SPF: pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 50.56.192.79 as permitted sender) client-ip=50.56.192.79; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 50.56.192.79 as permitted sender) smtp.mail=sup-devel-bounces@rubyforge.org; dkim=neutral (bad format) header.i=@gmail.com Received: from localhost.localdomain (localhost [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 2BE752E126; Mon, 13 May 2013 23:23:06 +0000 (UTC) X-Greylist: delayed 404 seconds by postgrey-1.31 at rubyforge; Mon, 13 May 2013 23:22:20 UTC Received: from mail-we0-f176.google.com (mail-we0-f176.google.com [74.125.82.176]) by rubyforge.org (Postfix) with ESMTP id 63A7D2E0F0 for ; Mon, 13 May 2013 23:22:20 +0000 (UTC) Received: by mail-we0-f176.google.com with SMTP id p60so6539415wes.7 for ; Mon, 13 May 2013 16:22:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:references:in-reply-to:subject:from:to:date :message-id:user-agent:content-transfer-encoding; bh=No5ekOQK6Ey0itah3062Yzorc3U8DIq7pbCz75gFBCE=; b=y2DPQ+E60KDdAx29XSDVMa78LkD+XgjrkNNcX63S/3ZySxyB9PZ0s6NBpHSLgqsopp RLSdgmScM0vKUQIDBDv9U2TWVlijdMXe4Dzk7UtUUb3wqQsj5H+A553dBTWHOEn/dTti JSus0Isz/eT6jEfGTNN1SLJujQGgUx/oSYXiCcamgnixwjtsblltKUC7t8btChVMOl7s bea3MkALvQO5qmTDeDxLjO02TRDZQS8KEka8ocZUcze9fNsxIOt2Uk5JsDoLM+azm+pV x8LRWD8Rhp3U59dOexcxDfyxUCj/eHhQMm02W9Bc7HPvkstoN+EA3NiFDmBcngIjEHPP CPhg== X-Received: by 10.180.206.238 with SMTP id lr14mr654306wic.24.1368486934390; Mon, 13 May 2013 16:15:34 -0700 (PDT) Received: from kpad (155-29-190-109.dsl.ovh.fr. [109.190.29.155]) by mx.google.com with ESMTPSA id a4sm20130021wic.5.2013.05.13.16.15.33 for (version=TLSv1.2 cipher=AES128-SHA bits=128/128); Mon, 13 May 2013 16:15:33 -0700 (PDT) Received: from localhost (1000@localhost [local]); by kpad (OpenSMTPD) with ESMTP id ce927408; for ; Mon, 13 May 2013 23:15:32 +0000 (UTC) References: <5188EB6E.8070504@gaute.vetsj.com> <51909A59.4030003@gaute.vetsj.com> In-reply-to: <51909A59.4030003@gaute.vetsj.com> From: Matthieu Rakotojaona To: sup-devel Date: Tue, 14 May 2013 01:15:31 +0200 Message-Id: <1368485829-sup-9105@kpad> User-Agent: Sup/git Subject: Re: [sup-devel] sup 0.13 - please test X-BeenThere: sup-devel@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Sup developer discussion List-Id: Sup developer discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-devel-bounces@rubyforge.org Errors-To: sup-devel-bounces@rubyforge.org Excerpts from Gaute Hope's message of lun. mai 13 09:46:33 +0200 2013: > > On 07. mai 2013 13:54, Gaute Hope wrote: > > On 28. april 2013 22:32, Hamish D wrote: > >> We'd like to get version 0.13 of sup out soon. There's a fair bit of > >> work gone into sup since 0.12 was released (in January 2011) that it > >> would be good to get out there. Once that is done we can then work on > >> the bigger goals we have for 0.14 - see > >> https://github.com/sup-heliotrope/sup/wiki/Development#roadmap for > >> those plans. > >> > >> So the question is, are there any serious bugs that we should fix > >> before releasing 0.13? > > > > Greetings sup-devel and sup-talk, > > > > > > Thanks to several contributors I think we should be getting ready for > > 0.13 now soon, we've removed a lot of old and deprecated stuff and > > generally cleaned a bit up. > > > > There is a new web page: http://supmua.org which is getting in shape and > > a wiki which is quickly growing: https://github.com/sup-heliotrope/sup/wiki > > > > We have forked our own version of ncursesw (ncursesw-sup) which now is a > > dependency for sup [1]. > > I think we are as good as we are going to get now. Unless something big > comes up we will release 0.13 on Wednesday. > > Regards, Gaute > Guys you are awesome. I am running sup like a breeze from ruby 1.8 with the gem built from the gemspec. I could even use the gpgme gem to sign/encrypt/decrypt/verify some emails, so it really is a huge thing to me. I do have a problem running with ruby 1.9 though, with xapian not launching correctly. -- Matthieu Rakotojaona _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel