rack-devel archive mirror (unofficial) https://groups.google.com/group/rack-devel
 help / color / mirror / Atom feed
From: Scytrin dai Kinthra <scytrin@gmail.com>
To: rack-devel@googlegroups.com
Subject: Re: Rack 1.0.1 maintenance release
Date: Mon, 5 Oct 2009 13:14:19 -0700	[thread overview]
Message-ID: <5a9d52bd0910051314t75865792xf1ea7e5b92c5d5cd@mail.gmail.com> (raw)
In-Reply-To: <m2vdl4bklt.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1234 bytes --]

Moving the openid stuff into rack-contrib for 1.1 sounds good. I am on a
vacation till the end of next week so as soon as I finish some personal
things I can do the migrations.

Additionally, as memcached ruby gem seems to be more stable with 0.17, I
plan on evaluating using that rather the memcache-client, unless there are
any objections.

--
stadik.net

On Aug 3, 2009 4:00 PM, "Christian Neukirchen" <chneukirchen@gmail.com>
wrote:


[Sorry for being rather inactive lately, my real life is too busy. ;)]

Joshua Peek <josh@joshpeek.com> writes: > I'd like to do a 1.0.1 maintenance
soon of the rack-1.0 ...
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.

> I went though most of the Lighthouse tickets and only found one that >
really concerned 1.0. > > ...
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.

blink, do you still want to split the openid parts?  1.1 would be a
good juncture.

Thanks to everyone,
--
Christian Neukirchen  <chneukirchen@gmail.com>  http://chneukirchen.org

[-- Attachment #2: Type: text/html, Size: 1768 bytes --]

  parent reply	other threads:[~2009-10-05 20: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
2009-10-05 20:14   ` Scytrin dai Kinthra [this message]
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=5a9d52bd0910051314t75865792xf1ea7e5b92c5d5cd@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).