From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.52.236.136 with SMTP id uu8csp26189vdc; Sun, 28 Apr 2013 13:39:34 -0700 (PDT) X-Received: by 10.236.128.198 with SMTP id f46mr31619980yhi.109.1367181574657; Sun, 28 Apr 2013 13:39:34 -0700 (PDT) Return-Path: Received: from rubyforge.org ([50.56.192.79]) by mx.google.com with ESMTP id j45si10254787yhl.239.2013.04.28.13.39.34 for ; Sun, 28 Apr 2013 13:39:34 -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 9EF802E0FC; Sun, 28 Apr 2013 20:39:35 +0000 (UTC) X-Greylist: delayed 393 seconds by postgrey-1.31 at rubyforge; Sun, 28 Apr 2013 20:39:22 UTC Received: from mail-vc0-f175.google.com (mail-vc0-f175.google.com [209.85.220.175]) by rubyforge.org (Postfix) with ESMTP id 77AF72E068 for ; Sun, 28 Apr 2013 20:39:22 +0000 (UTC) Received: by mail-vc0-f175.google.com with SMTP id lf10so4915552vcb.6 for ; Sun, 28 Apr 2013 13:39:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:from:date:message-id:subject:to :content-type; bh=4qkVfGT+h6Ds2dl8aYWn+PqaRx2MwS2/vPZspAU5duE=; b=meamJW7HylggvA3GU//4lIuZa6KpGaYCYiRvpfBYwnh8l4Jv4tWMGzv5IePKY/frKL rtIwPiBfIYkIqDPraZmRCXylz3vBmQHxYNokl8K4yHk3Jla0nmBtJZjsiwPP7IndnvBQ WsbxphE5YCbNu/tKWfz+bDvYnUVFJOErrpnokfLDOPJ/Umk+/tv7SclEbrepM1AfVrNP hbPS23JNltyE4u+l2OIw9B34jxvpJ2VUZ6W3ZOy9GSndAOL3DvSx8SPjI0XM9gs8gSrJ OrLZDWL3aJ4FAuhP8v/g0Jsxr/4/UWKapR4H8vzpN6SaK3XIXjM4cUEy0u1W5jSai71U H7Gw== X-Received: by 10.220.154.14 with SMTP id m14mr3991254vcw.21.1367181168307; Sun, 28 Apr 2013 13:32:48 -0700 (PDT) MIME-Version: 1.0 Received: by 10.221.3.194 with HTTP; Sun, 28 Apr 2013 13:32:08 -0700 (PDT) From: Hamish D Date: Sun, 28 Apr 2013 21:32:08 +0100 Message-ID: To: Sup developer discussion Subject: [sup-devel] sup 0.13 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: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-devel-bounces@rubyforge.org Errors-To: sup-devel-bounces@rubyforge.org 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? In particular are there any regressions from 0.12. I'm not aware of any at the moment. Looking at the issue list on github, there is: Invalid date in ncursesw gemspec for Ruby 1.8 https://github.com/sup-heliotrope/sup/issues/18 This is causing issues for gem installs. #30 is a possible fix that requires testing (by using ncurses-ruby instead of ncursesw). Could people try testing this branch on your own set up? Unable to add sources https://github.com/sup-heliotrope/sup/issues/33 This is another issue we should at least look into before a release. Any testing etc appreciated. If you have a burning issue that you think should be fixed in 0.13, please add it to the issue tracker now so we can decide. I've also lost track of what's gone on to the develop branch. Should 0.13 be based on the master branch or develop? Here's hoping we can get 0.13 out soon Hamish _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel