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-devel@googlegroups.com
Subject: Re: Rack 1.0.1 maintenance release
Date: Mon, 3 Aug 2009 20:43:06 -0500	[thread overview]
Message-ID: <1c5622660908031843j1aca35f1r96deb03143db0f4c@mail.gmail.com> (raw)
In-Reply-To: <m2vdl4bklt.fsf@gmail.com>


On Mon, Aug 3, 2009 at 5:25 PM, Christian
Neukirchen<chneukirchen@gmail.com> wrote:
> I'm open for Rack 1.1 suggestions.  1.1-discussed things can be merged
> into master now.
>
> I have more time to do a release cycle in the next few weeks, so if we
> merge quickly, we can push a 1.1 pretty soon.

For 1.1, I want to pull parts of Bryan Helmkamp's Rack::Test lib into
core. Its been proven and widely accepted by many frameworks so far. I
want to start a separate thread for this and we can discuss whats
important, what belongs in core, etc. 1.1 will give us a chance to
improve Rack's testing support.

http://github.com/brynary/rack-test/



-- 
Joshua Peek

  reply	other threads:[~2009-08-04  1:43 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 [this message]
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
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=1c5622660908031843j1aca35f1r96deb03143db0f4c@mail.gmail.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).