Hi all, There is a bug with Mongrel on JRuby 1.0.3 that the JRuby guys want fixed before they release it. If it''s ok with people I''d like to fix that, revert (at least for now) the proxy response change, and tag that as 1.1.2 and release it. Anything wrong with this plan? Evan -- Evan Weaver Cloudburst, LLC
Trunk looks kind of unstable now due to changes for 1.9, so I would build this off the 1.1.2 tag instead. Evan On Dec 14, 2007 7:47 PM, Evan Weaver <evan at cloudbur.st> wrote:> Hi all, > > There is a bug with Mongrel on JRuby 1.0.3 that the JRuby guys want > fixed before they release it. > > If it''s ok with people I''d like to fix that, revert (at least for now) > the proxy response change, and tag that as 1.1.2 and release it. > > Anything wrong with this plan? > > Evan > > -- > Evan Weaver > Cloudburst, LLC >-- Evan Weaver Cloudburst, LLC
1.1.1 rather. On Dec 14, 2007 8:41 PM, Evan Weaver <evan at cloudbur.st> wrote:> Trunk looks kind of unstable now due to changes for 1.9, so I would > build this off the 1.1.2 tag instead. > > Evan > > > On Dec 14, 2007 7:47 PM, Evan Weaver <evan at cloudbur.st> wrote: > > Hi all, > > > > There is a bug with Mongrel on JRuby 1.0.3 that the JRuby guys want > > fixed before they release it. > > > > If it''s ok with people I''d like to fix that, revert (at least for now) > > the proxy response change, and tag that as 1.1.2 and release it. > > > > Anything wrong with this plan? > > > > Evan > > > > -- > > Evan Weaver > > Cloudburst, LLC > > > > > > -- > Evan Weaver > Cloudburst, LLC >-- Evan Weaver Cloudburst, LLC
Yo, go for it. Changes for 1.9 (just 2, one changing "when ... :" for "when ... then" and other to the C code) are not a problem. But there are some other logging changes and maybe some other things around there, as we discussed in the irc. So it''s easier for you to use tag 1.1.1 and just backport the bug that was closed in trunk :) Let''s leave 1.9 compatibility and logging things for 1.2 release next year, along with some other cool ideas that may pop up until there. Cheers, filipe { @ icewall.org GPG 1024D/A6BA423E Jabber lautert at jabber.ru } On Fri, 14 Dec 2007, Evan Weaver wrote:> 1.1.1 rather. > > On Dec 14, 2007 8:41 PM, Evan Weaver <evan at cloudbur.st> wrote: >> Trunk looks kind of unstable now due to changes for 1.9, so I would >> build this off the 1.1.2 tag instead. >> >> Evan >> >> >> On Dec 14, 2007 7:47 PM, Evan Weaver <evan at cloudbur.st> wrote: >>> Hi all, >>> >>> There is a bug with Mongrel on JRuby 1.0.3 that the JRuby guys want >>> fixed before they release it. >>> >>> If it''s ok with people I''d like to fix that, revert (at least for now) >>> the proxy response change, and tag that as 1.1.2 and release it. >>> >>> Anything wrong with this plan? >>> >>> Evan >>> >>> -- >>> Evan Weaver >>> Cloudburst, LLC >>> >> >> >> >> -- >> Evan Weaver >> Cloudburst, LLC >> > > > > -- > Evan Weaver > Cloudburst, LLC > _______________________________________________ > Mongrel-development mailing list > Mongrel-development at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-development >
On Dec 14, 2007 11:32 PM, Filipe <filipe at icewall.org> wrote:> > Yo, go for it. Changes for 1.9 (just 2, one changing "when ... :" for > "when ... then" and other to the C code) are not a problem. But there are > some other logging changes and maybe some other things around there, as > we discussed in the irc. > > So it''s easier for you to use tag 1.1.1 and just backport the bug that > was closed in trunk :) > > Let''s leave 1.9 compatibility and logging things for 1.2 release next > year, along with some other cool ideas that may pop up until there. >+1 to Filipe comments. use 1.1.1 as base for 1.1.2 and we should start doing the 1.2 on a branch until we get something stable. Nice weekend everyone! -- Luis Lavena Multimedia systems - A common mistake that people make when trying to design something completely foolproof is to underestimate the ingenuity of complete fools. Douglas Adams
It''s done; tagged off of branches/stable_1-1. I packaged Ruby and cross-packaged Java from Rubygems 0.9.5 on OS X; I packaged Win32 from Rubygems 0.9.4 in Windows itself. Evan On Dec 14, 2007 9:53 PM, Luis Lavena <luislavena at gmail.com> wrote:> On Dec 14, 2007 11:32 PM, Filipe <filipe at icewall.org> wrote: > > > > Yo, go for it. Changes for 1.9 (just 2, one changing "when ... :" for > > "when ... then" and other to the C code) are not a problem. But there are > > some other logging changes and maybe some other things around there, as > > we discussed in the irc. > > > > So it''s easier for you to use tag 1.1.1 and just backport the bug that > > was closed in trunk :) > > > > Let''s leave 1.9 compatibility and logging things for 1.2 release next > > year, along with some other cool ideas that may pop up until there. > > > > +1 to Filipe comments. > > use 1.1.1 as base for 1.1.2 and we should start doing the 1.2 on a > branch until we get something stable. > > Nice weekend everyone! > > -- > Luis Lavena > Multimedia systems > - > A common mistake that people make when trying to design > something completely foolproof is to underestimate > the ingenuity of complete fools. > Douglas Adams > > _______________________________________________ > Mongrel-development mailing list > Mongrel-development at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-development >-- Evan Weaver Cloudburst, LLC
On Dec 14, 2007 9:32 PM, Filipe <filipe at icewall.org> wrote:> Let''s leave 1.9 compatibility and logging things for 1.2 release next > year, along with some other cool ideas that may pop up until there.Just an FYI, Kirk, Evan and I discussed adding Chunked encoding support also. Kirk said it''s simple so we''re going to target 1.2 for it. ~Wayne -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-development/attachments/20071215/726fe4b5/attachment.html