rack-devel archive mirror (unofficial) https://groups.google.com/group/rack-devel
 help / color / mirror / Atom feed
From: Joshua Peek <josh@joshpeek.com>
To: Rack Development <rack-devel@googlegroups.com>
Subject: Call for 1.1.0 release
Date: Mon, 21 Dec 2009 19:11:49 -0800 (PST)	[thread overview]
Message-ID: <9363563c-cbd4-498f-b9ee-b3ee83fa15b8@r5g2000yqb.googlegroups.com> (raw)

I'd to cut a 1.1 release before the new year. I'm going to put in the
work for the release notes and actual gem push. Now that we are on
Gemcutter, the entire rack core team has push access.

Heres an overview of the major changes:

* Relaxes SPEC to allow subclasses.
  - This is the major change I want to get out there. Right now Rails
2.x needs to monkey patch Lint to work around this.
* Refactored rackup into Rack::Server
* Removed Auth::OpenID
* Nested parameter and multipart generation improvements to Mock
* Pull in some useful contrib middleware: Config, ETag, Runtime,
Sendfile
* rack.logger extension specification
* Various bug fixes and optimizations

Please test rack/master and make sure your libraries are ready.

I'd like to get a +1 from all the rack core members before anything is
released.

             reply	other threads:[~2009-12-22  3:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-22  3:11 Joshua Peek [this message]
2009-12-22 13:02 ` Call for 1.1.0 release Christian Neukirchen
2009-12-22 22:52 ` Ryan Tomayko
2009-12-31  1:22   ` Eric Wong
2009-12-24 22:49 ` Eric Wong
2009-12-24 23:40   ` Joshua Peek
2009-12-24 23:57     ` Scytrin dai Kinthra
2009-12-25  0:24     ` Eric Wong
2009-12-26 14:41       ` James Tucker
2009-12-26 23:27         ` deferrable bodies in Rainbows! Eric Wong
2009-12-30 10:47           ` Eric Wong
2009-12-26 14:38     ` Call for 1.1.0 release James Tucker

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=9363563c-cbd4-498f-b9ee-b3ee83fa15b8@r5g2000yqb.googlegroups.com \
    --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).