From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (216.89-20-249.enivest.net. [89.20.249.216]) by mx.google.com with ESMTPSA id t17sm11334746lbd.11.2013.06.13.13.35.15 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Thu, 13 Jun 2013 13:35:19 -0700 (PDT) Date: Thu, 13 Jun 2013 22:33:28 +0200 From: Gaute Hope To: Sup developer discussion Message-ID: <1371155525-sup-5029@qwerzila> Subject: going for 0.13.1 and possibly 0.14? Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable User-Agent: Sup/git Greetings, as briefly discussed in #75 [1] some adjustments to the original plan sho= uld 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 no= t 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