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-devel@googlegroups.com, rack-core@googlegroups.com
Subject: Rack 1.1.1.pre, and notes on other potential releases
Date: Wed, 9 Feb 2011 19:24:09 -0800	[thread overview]
Message-ID: <1B0F767C-EF74-4684-B784-6659BA3A0854@gmail.com> (raw)

Hi All,

I have just pushed rack-1.1.1.pre. It's effectively up for rails testing (as they need it for the 2.x series release). I'm planning on pushing the same code base in roughly 24H if no issues arise.

I know many of you are keen for a 1.3 release. I want to do that when I have time. At present I'd really like to finish up 1.9 support, Multipart issues and correctly fix Encoding issues (our current included patches are wrong, as per Nahis advice). This will take some time, so I can't put a stake in the sand at this point.

As for a 1.2 release, I'd like to start prepping that ASAP (probably before the 1.3 release), but I haven't even looked at the water to see how much needs to be included.

There's more patch backlog to get through as well, that I'm well aware of. I'm also considering to make life easier, we might want to start phasing out Lighthouse. At this point it still has some valuable resources though, so we should get those enacted first.

Apologies to the rails folks for the long wait, and thanks for being patient.

Regards,

James Tucker

             reply	other threads:[~2011-02-10  3:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-10  3:24 James Tucker [this message]
2011-02-11 22:15 ` Rack 1.1.1.pre, and notes on other potential releases 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=1B0F767C-EF74-4684-B784-6659BA3A0854@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).