Archive of RubyForge sup-devel mailing list
 help / color / mirror / Atom feed
From: Gaute Hope <eg@gaute.vetsj.com>
To: Sup developer discussion <sup-devel@rubyforge.org>
Subject: going for 0.13.1 and possibly 0.14?
Date: Thu, 13 Jun 2013 22:33:28 +0200	[thread overview]
Message-ID: <1371155525-sup-5029@qwerzila> (raw)

Greetings,

as briefly discussed in #75 [1] some adjustments to the original plan should
be made. We were thinking:

  - Release another release in line-0.13 compatible with ruby 1.8 since
    we are starting to diverge in develop now. any efforts in fixing and
    maintaining ruby 1.8 support should be backported to this branch.

  - Work towards a 0.14 release with ruby 1.9 support on 'develop' and not
    necessarily with ruby 2.0 support yet. Already a several fixes have
    been done that have break ruby 1.8 which would be nice to get
    released in not too long.


Any thoughts?


Ruby 2.0: I am currently writing this from the tip of #61,
rmail-to-mail-inital [2]. Having successfully indexed >30k (except 1..)
of highly heterogeneous mails in all kinds of encodings. Tests are now
also working, as well as sending email obviously. Still lots of parts are
incomplete (e.g. no attachments yet..).

The effort to get to a sup with ruby 2.0 support (with maildir-syncback,
Mail - not RMail) has not reached a stable level. But I hope it could
get to a state where it makes sense to include it in a separate branch
in 'origin' so that it gets more available and easier to work against
for everybody.

Regards, Gaute

[1] https://github.com/sup-heliotrope/sup/pull/75
[2] https://github.com/sup-heliotrope/sup/pull/61



                 reply	other threads:[~2013-06-13 20:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1371155525-sup-5029@qwerzila \
    --to=eg@gaute.vetsj.com \
    --cc=sup-devel@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