unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: "Ernest W. Durbin III" <ewdurbin@gmail.com>
To: Eric Wong <e@80x24.org>
Cc: unicorn-public@bogomips.org
Subject: Re: dropping Ruby 1.8 support for unicorn 5?
Date: Sat, 27 Sep 2014 04:37:02 -0400	[thread overview]
Message-ID: <F149F002-B31D-4D02-8229-FEAB25681442@gmail.com> (raw)
In-Reply-To: <20140927083221.GA1390@dcvr.yhbt.net>

[-- Attachment #1: Type: text/plain, Size: 1404 bytes --]

As the submitter of the referenced 1.8.6 patch *still ashamed* I can say that I fully support a 4.x series with “maintenance” level support.

Since the language won’t be changing, the 4.x series should be a very quiet branch indeed.

Onward, to greater things.


On Sep 27, 2014, at 4:32 AM, Eric Wong <e@80x24.org> wrote:

> We've brought this up a few times, but I suppose we might as well drop
> 1.8 support in a major version change.
> We may still maintain unicorn 4.x for 1.8 users indefinitely; after all,
> we only accepted a patch for 1.8.6 compatibility less than a year
> ago(!)[1].   So I'll still feel a _little_ bad for dropping 1.8 :x
> One big reason for this is it looks like Ruby will move towards
> deprecating old Data_* macros for superior (1.9+-only) TypedData_*
> macros in the next few years[2].  The theme for unicorn 5 is mostly
> dropping old, unused crap anyways; and not gaining new bloat.
> Worst case is we support 1.8 and avoid deprecation warnings through
> the use of ifdefs in the HTTP parser, but I'm no fan of ifdefs.
> [1] commit 7e9e4c740aba24096f768f578779dc1053cb8b70
>    (construct listener_fds Hash in 1.8.6 compatible way)
> [2] http://svn.ruby-lang.org/cgi-bin/viewvc.cgi?view=revision&revision=47717
>    This is due to type-checking issues like
>    https://bugs.ruby-lang.org/issues/10296

  reply	other threads:[~2014-09-27  8:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-27  8:32 dropping Ruby 1.8 support for unicorn 5? Eric Wong
2014-09-27  8:37 ` Ernest W. Durbin III [this message]
2014-10-18 21:39 ` Eric Wong

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:

  List information: https://yhbt.net/unicorn/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=F149F002-B31D-4D02-8229-FEAB25681442@gmail.com \
    --to=ewdurbin@gmail.com \
    --cc=e@80x24.org \
    --cc=unicorn-public@bogomips.org \


* 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.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).