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: Friends of Rack ∩ Friends of JRuby (was Re: Rack test spec_rack_runtime fails on JRuby due to timing)
Date: Mon, 18 Jan 2010 11:51:56 -0600	[thread overview]
Message-ID: <1c5622661001180951gd3fea06v2e169b27b184a766@mail.gmail.com> (raw)
In-Reply-To: <f04d2211001180928y38bbb09cw62dc2c15269917b3@mail.gmail.com>

+1 for any Rack CI. We have nothing right now.

On Mon, Jan 18, 2010 at 11:28 AM, Charles Oliver Nutter
<headius@headius.com> wrote:
> If we get this green, I may advocate we set up a CI build for
> JRuby+Rack somewhere. We've got a server (ci.jruby.org) where we could
> put it, and it's obviously a pretty critical piece of infrastructure.
>
> As for JRuby actives on the Rack lists...I'm not sure...
>
> On Mon, Jan 18, 2010 at 12:42 AM, Ryan Tomayko <r@tomayko.com> wrote:
>> On Sun, Jan 17, 2010 at 10:20 AM, Charles Oliver Nutter
>> <headius@headius.com> wrote:
>>> This came up because a friend of JRuby is working to prepare a Gentoo
>>> ebuild, and wants to get all related packages running green.
>>
>> Speaking of, are there any friends of JRuby that are active on the
>> rack list? It'd be cool if someone could sign up for ensuring the test
>> suite is green before shipping new releases.
>>
>> Thanks,
>> Ryan
>>
>



-- 
Joshua Peek

  reply	other threads:[~2010-01-18 17:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-18  6:42 Friends of Rack ∩ Friends of JRuby (was Re: Rack test spec_rack_runtime fails on JRuby due to timing) Ryan Tomayko
2010-01-18 17:28 ` Charles Oliver Nutter
2010-01-18 17:51   ` Joshua Peek [this message]
2010-01-18 21:04   ` Nick Sieger
2010-01-18 22:19     ` Charles Oliver Nutter
2010-01-19  5:43       ` Nick Sieger
2010-01-19 23:23         ` Eric Wong
2010-01-20 18:08           ` Nick Sieger
2010-01-20 18:10             ` Nick Sieger

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=1c5622661001180951gd3fea06v2e169b27b184a766@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).