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]. To be able to do the next release we need some testing of the current state of 'develop' and the new ncursesw-sup gem. For instructions on how to help out with testing the latest git version (develop) check out: https://github.com/sup-heliotrope/sup/wiki/Running-from-git If you have any problems or questions please ask. Report issues to: https://github.com/sup-heliotrope/sup/issues [1] https://rubygems.org/gems/ncursesw-sup Regards, Gaute _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel
