From: Gaute Hope <eg@gaute.vetsj.com>
To: sup-devel@rubyforge.org, sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-devel] sup 0.13 - please test
Date: Tue, 07 May 2013 13:54:22 +0200 [thread overview]
Message-ID: <5188EB6E.8070504@gaute.vetsj.com> (raw)
In-Reply-To: <CAOxvSbeLRoCwy2THkKa4TKsNqdsx9n-M5BxrZHGfPEUjfEWjSg@mail.gmail.com>
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
parent reply other threads:[~2013-05-07 11:55 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAOxvSbeLRoCwy2THkKa4TKsNqdsx9n-M5BxrZHGfPEUjfEWjSg@mail.gmail.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5188EB6E.8070504@gaute.vetsj.com \
--to=eg@gaute.vetsj.com \
--cc=sup-devel@rubyforge.org \
--cc=sup-talk@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox