[lnkForumImage]
TotalShareware - Download Free Software

Confronta i prezzi di migliaia di prodotti.
Asp Forum
 Home | Login | Register | Search 


 

Forums >

comp.lang.ruby

Next stable 1.9.x

Michael Malone

3/4/2009 10:03:00 PM

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.
=======================================================================


5 Answers

Jason Roelofs

3/4/2009 10:34:00 PM

0

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/versio...

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 stabl=
e
> release (1.9.2)?
>
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> This email, including any attachments, is only for the intended
> addressee. =A0It 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.
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
>
>

Robert Dober

3/5/2009 9:14:00 PM

0

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 stabl=
e
> release (1.9.2)?
>
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> This email, including any attachments, is only for the intended
> addressee. =A0It 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

Michael Malone

3/5/2009 9:27:00 PM

0

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.
=======================================================================


Jeff Schwab

3/5/2009 9:50:00 PM

0

Michael Malone wrote:
> Robert Dober wrote:
>> On Wed, Mar 4, 2009 at 11:02 PM, Michael Malone
>> <michael.malone@tait.co.nz> 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.

Len

2/3/2010 2:36:00 AM

0

Joel,

I think I have a problem to use ADO method for several excel files
that had already been completed ( ie budget files already submitted
from 25 profit centers (BAI) and 22 cost centers (BAII) respectively
under budget directory(dem3) with 2 folders namely BAI and BAII
folders)

Now the problem is all budget files submitted with incorrect row
header format so I need to refill up the row header under column B in
one worksheet("P+L") from every budget file and thereafter I will
create named range in that "P+L" worksheet of every budget file. Later
I will proceed to create a summary budget via data consolidation

For data consolidate function, I will use keys selection of row,
column headers and create link to data source.

I'm in puzzle to which method is the most appropriate to run this
batch of excel files for data consolidation purpose, please advise

Regards
Len