From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from [192.168.1.42] (216.89-20-249.enivest.net. [89.20.249.216]) by mx.google.com with ESMTPS id m1sm6235151lbh.5.2013.03.26.00.12.07 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 26 Mar 2013 00:12:07 -0700 (PDT) Message-ID: <51514A36.5040907@gaute.vetsj.com> Date: Tue, 26 Mar 2013 08:11:50 +0100 From: Gaute Hope User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130311 Thunderbird/17.0.4 MIME-Version: 1.0 To: sup-talk Subject: Travis integration References: In-Reply-To: X-Enigmail-Version: 1.5.1 X-Forwarded-Message-Id: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Hi, Travis integration: I think this is a good idea, especially if we get more tests up and running. My biggest annoyance, charset-issues, could potentially greatly benefit from this. Every time something new is implemented or something is changed it is very easy to forget to test for ASCII / UTF-8 / whatever conversion/mixing and so on, it would be great with a general test that could be easily adapted for theses cases. @Whyme: How does your Travis integration work with the new 'test' target? What do you think about including the few files that are in the main repositories? - Gaute -------- Original Message -------- Subject: Re: [sup] Convert use of Rake::GemPackageTask to Gem::PackageTask (#9) Date: Thu, 21 Mar 2013 08:04:54 -0700 From: Whyme.Lyu Reply-To: sup-heliotrope/sup To: sup-heliotrope/sup CC: Gaute Hope +1 for merging this. With this patch and #10 and #11 applied, I can do `rake gem` locally. And I'm about to setup Travis integration. Even if there're no tests, it'd be much better to just do a smoking build and release a usable gem soon. --- Reply to this email directly or view it on GitHub: https://github.com/sup-heliotrope/sup/pull/9#issuecomment-15243758