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 <notificati...@github.com> Reply-To: sup-heliotrope/sup <reply+i-11837079-94d5e391deb98d79554cc13e2825e2d1dcf6c79a-56...@reply.github.com> To: sup-heliotrope/sup <s...@noreply.github.com> CC: Gaute Hope <e...@gaute.vetsj.com> +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 _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
