rack-devel archive mirror (unofficial) https://groups.google.com/group/rack-devel
 help / color / mirror / Atom feed
From: Alastair Pharo <asppsa@gmail.com>
To: rack-devel@googlegroups.com
Subject: Any plans to drop Ruby 2.2 support from Rack?
Date: Tue, 20 Mar 2018 00:34:19 +1100	[thread overview]
Message-ID: <87d100ur38.fsf@louros.polinaro.space> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1697 bytes --]

Hi there,

I am one of the maintainers of [Moneta][1].  Until a couple of days ago
we were still testing against a rather ancient set of MRI Ruby versions,
but we have just decided we need to modernise, and as part of that the
question of what sort of policy we should have concerning the minimum
supported Ruby version (i.e. `required_ruby_version` in the
gemspec) has arisen.

Because Moneta is designed for use with web projects that mostly depend
on Rack, we thought we would follow Rack's lead on this, so that anyone
who is able to use Rack can also use Moneta.  This has of course lead us
to wondering what the Rack team's policy on this is.  Do you think it
makes sense to phase out MRI rubies once they have EOLed, or do you
think there is virtue in maintaining support for older versions beyond
that?  As Ruby 2.2 will be EOLed at the end of this week, we are keen to
know if you think there is merit in maintaining 2.2 support beyond that
time.

Also, my own understanding of how gem semver should fit with minimum
Ruby versions is not that clear.  I see that Rack introduced the `>=
2.2.0` requirement with v2 of the gem, so do you think that changing the
minimum Ruby from say, 2.2 to 2.3 should only be done as part of a major
version change of the gem?

I'm very keen to hear your thoughts on any or all of the above.  Thanks
in advance!

-Alastair

[1]: https://github.com/minad/moneta

-- 

--- 
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 #1.2: Type: text/html, Size: 2091 bytes --]

                 reply	other threads:[~2018-03-19 14: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-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=87d100ur38.fsf@louros.polinaro.space \
    --to=rack-devel@googlegroups.com \
    /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).