From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from [129.177.117.174] ([129.177.117.174]) by mx.google.com with ESMTPSA id bj12sm21077554eeb.8.2013.05.13.00.47.53 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 13 May 2013 00:47:53 -0700 (PDT) Message-ID: <51909A59.4030003@gaute.vetsj.com> Date: Mon, 13 May 2013 09:46:33 +0200 From: Gaute Hope User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130403 Thunderbird/17.0.5 MIME-Version: 1.0 To: sup-devel@rubyforge.org Subject: Re: [sup-devel] sup 0.13 - please test References: <5188EB6E.8070504@gaute.vetsj.com> In-Reply-To: <5188EB6E.8070504@gaute.vetsj.com> X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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