Mongrel users - Jul 2006 - Mongrel 0.3.13.4 Pre-Release -- All Fixed Up Now

Hello Everyone,

This is a short announce to get people to try the 0.3.13.4 pre-release
with their applications.  This release features a few things that folks
have asked for, and a backport of an enhancement from the 0.4 release
coming later.

The features are:

1) A new --prefix command line option for people who want to mount their
rails app at a different base URI.  Thanks to Scott for the initial
push.
2) Fixes for the upcoming upload progress support (from Rick).
3) Pound documentation changes (MUST READ if you use pound).
4) Fix for a very rare case where the GC can cause a segfault
theoretically.

Everyone should test this release out, and I''ll be thrashing it with
RFuzz this weekend to do a release tomorrow night.

This will also be the last release before 0.4 Enterprise Edition 1.2.
All my work from now on will go to the EE release unless there''s a
major
security hole or bug.


-- 
Zed A. Shaw
http://www.zedshaw.com/
http://mongrel.rubyforge.org/
http://www.railsmachine.com/ -- Need Mongrel support?

Hi!

On Sat, Jul 15, 2006 at 07:08:50PM -0400, Zed Shaw
wrote:
> Hello Everyone,
> 
> This is a short announce to get people to try the 0.3.13.4 pre-release
> with their applications.  This release features a few things that folks
> have asked for, and a backport of an enhancement from the 0.4 release
> coming later.
works fine for me so far. 

Btw, would it be possible to create svn tags for the revisions that
correspond to released versions ? Or at least state somewhere which
exact revision a release is made from ? That way I could create the
Debian packages off the exact same revision instead having to export
trunk right after the release, hoping it''s still the released revision.

Regards,
Jens


-- 
webit! Gesellschaft f?r neue Medien mbH          www.webit.de
Dipl.-Wirtschaftsingenieur Jens Kr?mer       kraemer at webit.de
Schnorrstra?e 76                         Tel +49 351 46766  0
D-01069 Dresden                          Fax +49 351 46766 66

On Sun, 2006-07-16 at 10:08 +0200, Jens Kraemer wrote:
> Btw, would it be possible to create svn tags for the revisions that
> correspond to released versions ? Or at least state somewhere which
> exact revision a release is made from ? That way I could create the
> Debian packages off the exact same revision instead having to export
> trunk right after the release, hoping it''s still the released
revision.
Right now (and this will change soon), it''s organized this way:

  /mongrel/branches/mongrel-0.4 mongrel-0.4
  /mongrel/trunk                mongrel_stable

That''s off of the base svn so you should be good.  So, the 0.3.13.4
stream (stable) is in trunk, and my current work is being done in the
branches/mongrel-0.4 location.

I''ll do a tag for the next release, but god I hate svn''s tags.
If it
weren''t for svk I''d avoid it entirely.

-- 
Zed A. Shaw
http://www.zedshaw.com/
http://mongrel.rubyforge.org/
http://www.railsmachine.com/ -- Need Mongrel support?

On Sun, Jul 16, 2006 at 04:21:50AM -0400, Zed Shaw
wrote:
> On Sun, 2006-07-16 at 10:08 +0200, Jens Kraemer wrote:
> > Btw, would it be possible to create svn tags for the revisions that
> > correspond to released versions ? Or at least state somewhere which
> > exact revision a release is made from ? That way I could create the
> > Debian packages off the exact same revision instead having to export
> > trunk right after the release, hoping it''s still the released
revision.
> 
> Right now (and this will change soon), it''s organized this way:
> 
>   /mongrel/branches/mongrel-0.4 mongrel-0.4
>   /mongrel/trunk                mongrel_stable
> 
> That''s off of the base svn so you should be good.  So, the
0.3.13.4
> stream (stable) is in trunk, and my current work is being done in the
> branches/mongrel-0.4 location.
ah, ok :-). 

Seems I use svn different than you - I commit to trunk all the time
between revisions of a project, so trunk usually is pretty unstable in
my repositories. 
> I''ll do a tag for the next release, but god I hate svn''s
tags.  If it
> weren''t for svk I''d avoid it entirely.
Thanks! 
Just out of curiosity - what do you think is wrong with svn tags ?

Jens

-- 
webit! Gesellschaft f?r neue Medien mbH          www.webit.de
Dipl.-Wirtschaftsingenieur Jens Kr?mer       kraemer at webit.de
Schnorrstra?e 76                         Tel +49 351 46766  0
D-01069 Dresden                          Fax +49 351 46766 66

ok, i give up, i cannot find these changes - if it''s just to advise of
the
x-forwarded issues then that''s ok, but if it''s a
solution/anything else can
you please point me in the right direction!

cheers

On Sunday 16 July 2006 00:08, Zed Shaw wrote:
> 3) Pound documentation changes (MUST READ if you use pound).

On Mon, 2006-07-17 at 15:22 +0100, Scott Mathieson
wrote:
> ok, i give up, i cannot find these changes - if it''s just to
advise of the
> x-forwarded issues then that''s ok, but if it''s a
solution/anything else can
> you please point me in the right direction!
> 
> cheers
> 
> On Sunday 16 July 2006 00:08, Zed Shaw wrote:
> > 3) Pound documentation changes (MUST READ if you use pound).
Sorry, the configuration used to read like:

Service
    BackEnd
      Address 127.0.0.1
      Port    8000
    End
  End
  Service
    BackEnd
      Address 127.0.0.1
      Port    8001
    End
  End
  Service
    BackEnd
      Address 127.0.0.1
      Port    8002
    End
  End

Which meant there was no failover.

There was also an old copy on last night but I put the right ones up.
Just make sure you follow the new docs (which have all three
Backends inside one Service).


-- 
Zed A. Shaw
http://www.zedshaw.com/
http://mongrel.rubyforge.org/
http://www.railsmachine.com/ -- Need Mongrel support?

cheers Jan/Zed, thought i''d missed something new
On Monday 17 July 2006 15:30, you wrote:
> > On Sunday 16 July 2006 00:08, Zed Shaw wrote:
> > > 3) Pound documentation changes (MUST READ if you use pound).
>
> Sorry, the configuration used to read like:
>
> Service
>     BackEnd
>       Address 127.0.0.1
>       Port    8000
>     End
>   End
>   Service
>     BackEnd
>       Address 127.0.0.1
>       Port    8001
>     End
>   End
>   Service
>     BackEnd
>       Address 127.0.0.1
>       Port    8002
>     End
>   End
>
> Which meant there was no failover.
>
> There was also an old copy on last night but I put the right ones up.
> Just make sure you follow the new docs (which have all three
> Backends inside one Service).