Next stable 1.9.x

Does anyone know if there's a projected timeline for the next 1.9.x stable release (1.9.2)?

···

=======================================================================
This email, including any attachments, is only for the intended
addressee. It is subject to copyright, is confidential and may be
the subject of legal or other privilege, none of which is waived or
lost by reason of this transmission.
If the receiver is not the intended addressee, please accept our
apologies, notify us by return, delete all copies and perform no
other act on the email.
Unfortunately, we cannot warrant that the email has not been
altered or corrupted during transmission.

I hope it's quick. One of the extensions I work with and on (Rice)
dies horribly with 1.9.1 when exceptions are thrown, and works
wonderfully under the current trunk (1.9.2dev).

This is the best information I could find on this question:

http://redmine.ruby-lang.org/versions/show/11

Jason

···

On Wed, Mar 4, 2009 at 5:02 PM, Michael Malone <michael.malone@tait.co.nz> wrote:

Does anyone know if there's a projected timeline for the next 1.9.x stable
release (1.9.2)?

=======================================================================
This email, including any attachments, is only for the intended
addressee. It is subject to copyright, is confidential and may be
the subject of legal or other privilege, none of which is waived or
lost by reason of this transmission.
If the receiver is not the intended addressee, please accept our
apologies, notify us by return, delete all copies and perform no
other act on the email.
Unfortunately, we cannot warrant that the email has not been
altered or corrupted during transmission.

Meaning, we should ignore this?

Sorry no info on your question, but I could not resist whacking at
those "legal obligations".

Cheers
Robert

···

On Wed, Mar 4, 2009 at 11:02 PM, Michael Malone <michael.malone@tait.co.nz> wrote:

Does anyone know if there's a projected timeline for the next 1.9.x stable
release (1.9.2)?

=======================================================================
This email, including any attachments, is only for the intended
addressee. It is subject to copyright, is confidential and may be
the subject of legal or other privilege, none of which is waived or
lost by reason of this transmission.
If the receiver is not the intended addressee, please accept our
apologies, notify us by return, delete all copies and perform no
other act on the email.
Unfortunately, we cannot warrant that the email has not been
altered or corrupted during transmission.

Robert Dober wrote:

···

On Wed, Mar 4, 2009 at 11:02 PM, Michael Malone > <michael.malone@tait.co.nz> wrote:
  

Does anyone know if there's a projected timeline for the next 1.9.x stable
release (1.9.2)?

=======================================================================
This email, including any attachments, is only for the intended
addressee. It is subject to copyright, is confidential and may be
the subject of legal or other privilege, none of which is waived or
lost by reason of this transmission.
If the receiver is not the intended addressee, please accept our
apologies, notify us by return, delete all copies and perform no
other act on the email.
Unfortunately, we cannot warrant that the email has not been
altered or corrupted during transmission.
    

Meaning, we should ignore this?

Sorry no info on your question, but I could not resist whacking at
those "legal obligations".

Cheers
Robert

Yeah, our mail server attaches them to every outgoing message. Corporations: Adding unenforceable cruft to untraceable messages since 1992

Michael

And here's another for you:

=======================================================================
This email, including any attachments, is only for the intended
addressee. It is subject to copyright, is confidential and may be
the subject of legal or other privilege, none of which is waived or
lost by reason of this transmission.
If the receiver is not the intended addressee, please accept our
apologies, notify us by return, delete all copies and perform no
other act on the email.
Unfortunately, we cannot warrant that the email has not been
altered or corrupted during transmission.

Michael Malone wrote:

Robert Dober wrote:

This email, including any attachments, is only for the intended
addressee. It is subject to copyright, is confidential and may be

[...]

Sorry no info on your question, but I could not resist whacking at
those "legal obligations".

Yeah, our mail server attaches them to every outgoing message. Corporations: Adding unenforceable cruft to untraceable messages since 1992

If you put a "-- " line at the end of your email, it might at least make the cruft look like an ordinary sig.

···

On Wed, Mar 4, 2009 at 11:02 PM, Michael Malone >> <michael.malone@tait.co.nz> wrote: