From: Aaron Patterson <tenderlove@ruby-lang.org>
To: rack-devel@googlegroups.com
Cc: Aaron Patterson <tenderlove@ruby-lang.org>,
Adam Duke <adamduke@twitter.com>,
unicorn-public@bogomips.org
Subject: Re: [PATCH] limit rack version for ruby compatibility
Date: Fri, 8 Jan 2016 15:19:10 -0800 [thread overview]
Message-ID: <20160108231910.GA42107@TC.local> (raw)
In-Reply-To: <20160108223732.GA28771@dcvr.yhbt.net>
[-- Attachment #1: Type: text/plain, Size: 2108 bytes --]
On Fri, Jan 08, 2016 at 10:37:32PM +0000, Eric Wong wrote:
> Aaron Patterson <tenderlove@ruby-lang.org> wrote:
> > The main reason I bumped it up to Ruby 2.2.x is because that will be the
> > minimum version of Ruby I'll be stuck with throughout Rack 2.x's
> > lifetime. IOW, I can't drop Ruby versions in anything but a major
> > release so I'm being conservative and only going with the latest (at the
> > time that was 2.2).
> >
> > I could be convinced to bring down the version number, but I'd like to
> > know why first. :)
>
> Because other people are _always_ slow to upgrade :)
Yes, exactly. I am betting that by the time people upgrade to Rack 2.0,
Ruby 2.2.2 will be old hat (Ruby 2.3 has been released already!) ;)
> However, I suppose it's fine to bring the requirement up with a
> major version bump of Rack. I don't want to burden you with
> old cruft, either.
>
> unicorn may also be able to drop the dependency on rack by
> lazy loading:
>
> * Rack::Utils::HTTP_STATUS_CODES is the main thing we use from
> Rack at runtime; and unicorn would actually function fine if
> the hash were empty; HTTP status lines would just be short
> and non-descriptive.
>
> * The Rack::Builder dependency can be optional, even.
>
> Fwiw, I plan to support Rack 1.x and Ruby 1.9.3 under unicorn for a few
> more years because of LTS distros. New versions take priority, of
> course.
Ok. Let me know if there's anything I can do to help. Removing the
strict requirement from the gemspec *is* on the table, as long as we
document the supported versions in the README. I don't plan on using
anything that would be specific to Ruby 2.2.2 and up, but I don't want
to be burdened by older ones either. A simple comment in the README
would suffice.
--
Aaron Patterson
http://tenderlovemaking.com/
--
---
You received this message because you are subscribed to the Google Groups "Rack Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rack-devel+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #2: Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2016-01-08 23:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CACj6Wog0=R6Wsh1U5SFE6r1BdWBr4Loe+GM6UKdObSALwAj9JQ@mail.gmail.com>
2016-01-08 19:18 ` [PATCH] limit rack version for ruby compatibility Eric Wong
2016-01-08 21:50 ` Aaron Patterson
2016-01-08 21:56 ` Aaron Patterson
[not found] ` <CACj6WohuY65xCNVRwrA4ODrj1NcsMNaDBw8ykxJ6YBAhZ4ZU4Q@mail.gmail.com>
2016-01-08 22:17 ` Aaron Patterson
2016-01-08 22:37 ` Eric Wong
2016-01-08 23:19 ` Aaron Patterson [this message]
[not found] ` <CACj6Wog+1rqEaW1R1G0eKEZuz7vNVUC51Qh7q7Z1tKpzRrybKw@mail.gmail.com>
2016-01-21 20:12 ` Eric Wong
2016-01-21 22:09 ` Aaron Patterson
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-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://groups.google.com/group/rack-devel
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160108231910.GA42107@TC.local \
--to=rack-devel@googlegroups.com \
--cc=adamduke@twitter.com \
--cc=tenderlove@ruby-lang.org \
--cc=unicorn-public@bogomips.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).