From: Joshua Peek <josh@joshpeek.com>
To: Rack Development <rack-devel@googlegroups.com>
Subject: Re: Rack 1.0.1 maintenance release
Date: Mon, 5 Oct 2009 10:15:48 -0700 (PDT) [thread overview]
Message-ID: <f628706a-0161-46b7-9344-9bd291914245@s6g2000vbp.googlegroups.com> (raw)
In-Reply-To: <f732822d0908090050l76983077s36ce6d37e771c6b2@mail.gmail.com>
Please!
On Aug 9, 2:50 am, Ryan Tomayko <r...@tomayko.com> wrote:
> On Tue, Aug 4, 2009 at 7:22 PM, Joshua Peek<j...@joshpeek.com> wrote:
>
> > On Mon, Aug 3, 2009 at 5:25 PM, Christian
> > Neukirchen<chneukirc...@gmail.com> wrote:
> >>> I'd like to do a 1.0.1 maintenance soon of the rack-1.0 branch. Please
> >>> test your apps and frameworks on that branch. It should be a fully
> >>> compatible bug fix release.
>
> >> This is a good idea. When you consider it ready, I can write an
> >> announcement and do a formal release on Rubyforge and my servers.
>
> > Rails 2.3 is all systems go w/ rack 1.0.1.
>
> > Should wait on Ryan to test w/ Sinatra.
>
> Sorry. I'm way behind on ML/lighthouse duties.
>
> Sinatra looks good under the rack-1.0 branch. +1 for release.
>
> The Sinatra test suite fails like crazy under 1.9 due to this
> rack.input / external encoding Rack::Lint check:
>
> http://github.com/rack/rack/commit/851782648fbbb141b1b56b73d8efc99efc...
>
> The Sinatra test suite puts Rack::Lint in the middleware pipeline for
> every test, though. I don't think that's a common practice. It passes
> 100% when I remove that check. The issue seems to be with the way
> Rack::MockRequest wraps the :input string in an StringIO without any
> encoding work. Or, maybe we should be setting the encoding on the
> input string before passing it in. I should be able to work around
> this in Sinatra somehow.
>
> Thanks,
> Ryan
next prev parent reply other threads:[~2009-10-05 17:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-03 17:36 Rack 1.0.1 maintenance release Joshua Peek
2009-08-03 22:25 ` Christian Neukirchen
2009-08-04 1:43 ` Joshua Peek
2009-08-05 19:36 ` Christian Neukirchen
2009-08-04 4:16 ` Joshua Peek
2009-08-05 2:22 ` Joshua Peek
2009-08-09 7:50 ` Ryan Tomayko
2009-10-05 17:15 ` Joshua Peek [this message]
2009-10-05 20:14 ` Scytrin dai Kinthra
2009-10-06 14:06 ` Christian Neukirchen
2009-10-06 14:18 ` James Tucker
2009-10-06 14:27 ` Christian Neukirchen
2009-10-14 5:49 ` Quin Hoxie
2009-10-16 20:30 ` Christian Neukirchen
2009-10-16 21:08 ` Daniel Rodríguez Troitiño
2009-10-16 23:58 ` Christian Neukirchen
2009-08-04 4:15 ` James
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=f628706a-0161-46b7-9344-9bd291914245@s6g2000vbp.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).