rack-devel archive mirror (unofficial) https://groups.google.com/group/rack-devel
 help / color / mirror / Atom feed
From: James Tucker <jftucker@gmail.com>
To: rack-core@googlegroups.com, rack-devel@googlegroups.com
Subject: 1.1 Roadmap / EOL
Date: Thu, 8 Sep 2011 12:33:55 -0700	[thread overview]
Message-ID: <787C9DA2-5CBC-43A3-B9FA-A984A3689DA7@gmail.com> (raw)

Hi all,

I really want to EOL 1.1. There are some patches I'm bringing in for the (late - sorry) security releases, and to get Rails 2.x cookie issues sorted.

I want to attach a provisional EOL statement to the README in the 1.1.3 release. Rails is also gearing up to EOL the 2.x series.

If there are any more "critical" security patches, I may consider another patch release, but essentially, I want to encourage the community not to expect further maintenance of the 1.1 series.

Does anyone have any major objections? I would like to point out that I spotted more than a handful of quite serious bugs in the rails 2.x and rack 1.1.x render + cookie stack on the way through, and will not be fixing all of them in this upcoming release.

I would STRONGLY (in the most vehement definition) recommend upgrading your apps to rails > 2 and rack > 1.1 regardless of the outcome of any further discussions.

Thanks for your attention/input,

James

             reply	other threads:[~2011-09-08 19:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-08 19:33 James Tucker [this message]
2011-09-08 19:50 ` 1.1 Roadmap / EOL Christian Neukirchen

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=787C9DA2-5CBC-43A3-B9FA-A984A3689DA7@gmail.com \
    --to=rack-devel@googlegroups.com \
    --cc=rack-core@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).