From: Rocky Bernstein Date: 2008-03-04T07:15:26+09:00 Subject: Re: Schedule for the 1.8.7 release ------=_Part_2464_26395784.1204582534516 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline I'm a little confused with what you are asking, so let me try to summarize. I have two requests for the release so far. The first change request is a patch by Mauricio Fernandez. It has been applied to Ruby 1.9 although Mauricio also gave a patch for 1.8 and it is just as valid there. The second change request stems from an observation that in conditionals like "if", "while", or "until", a trace hook gets called twice for no good reason that I can tell. Originally I had thought there was a stop before the expression was evaluated and another after the expression was evaluated, but that is not the case. Here is an example: x=1 x=2 if x=3 If you debug this you will see that the values of x are 1 and 2 even though there is a stage in theory where x=3. I'm not sure what the intended behavior is supposed to be, but if it is to run the trace hook once, I think I could provide a patch for that. On Ruby 1.9 if you run the above program, I do not believe you do not get the duplicate call to the trace hook. Since Ruby 1.9 changes constantly, I could be wrong; so folks please double check. I have been using a patched debug.rb on 1.9 since the one I have installed on Ubuntu ruby 1.9.0(2007-08-30 patchlevel 0) [i486-linux] doesn't work. (No doubt this been subsequently fixed.) On Mon, Mar 3, 2008 at 4:09 PM, Akinori MUSHA wrote: > Still packing.. > > At Mon, 3 Mar 2008 09:41:23 -0500, > Rocky Bernstein wrote: > > comments in line. > > > > On Sat, Mar 1, 2008 at 6:58 AM, Akinori MUSHA wrote: > > > > > Hi, developers, > > > > > > After seeing Ruby 1.9.0-1 released earlier today, I, as the release > > > manager of the 1.8 series, would like to announce here that it is time > > > to start working on the next release, 1.8.7. > > > > > > Below is the timeline I made up. The reason for the slow start (long > > > period for discussion) is because I'm going on a week's trip next week > > > to Portland and Seattle. > > > > > > Schedule for 1.8.7: (subject to change as it proceeds) > > > > > > Now - 2008-03-22 > > > Discuss what features should and/or can be backported, and get > > > the release manager to make decisions as to which features are > > > going to be worked on for 1.8.7. > > > > > > > In what forum are changes and features going to be discussed? ruby-core? > As > > Yes, ruby-core would be the best place to discuss in. > > > for issues, > > see http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-core/15231 > > > > Alas no comments/discussion. If you want me to work up a patch, let me > know. > > > > As for back-ports, I have the honor of submitting the first tracker > request > > :-) > > > > > http://rubyforge.org/tracker/index.php?func=detail&aid=18517&group_id=426&atid=22040 > > OK, I've read the thread and the patch looks fair. But, is what you > mean by "a patch" different than is attached to the request? > > -- > Akinori MUSHA / http://akinori.org/ > ------=_Part_2464_26395784.1204582534516 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline I'm a little confused with what you are asking, so let me try to summarize.

I have two requests for the release so far. The first change request is a patch by Mauricio Fernandez. It has been applied to Ruby 1.9 although Mauricio also gave a patch for 1.8 and it is just as valid there.

The second change request stems from an observation that in conditionals like "if", "while", or "until", a trace hook gets called twice for no good reason that I can tell. Originally I had thought there was a stop before the expression was evaluated and another after the expression was evaluated, but that is not the case.

Here is an example:

x=1
x=2 if x=3

If you debug this you will see that the values of x are 1 and 2 even though there is a stage in theory where x=3.

I'm not sure what the intended behavior is supposed to be, but if it is to run the trace hook once, I think I could provide a patch for that.

On Ruby 1.9 if you run the above program, I do not believe you do not get the duplicate call to the trace hook. Since Ruby 1.9 changes constantly, I could be wrong; so folks please double check. I have been using a patched debug.rb on 1.9 since the one I have installed on Ubuntu ruby 1.9.0 (2007-08-30 patchlevel 0) [i486-linux] doesn't work. (No doubt this been subsequently fixed.)

On Mon, Mar 3, 2008 at 4:09 PM, Akinori MUSHA <knu@idaemons.org> wrote:

Still packing..

At Mon, 3 Mar 2008 09:41:23 -0500,

Rocky Bernstein wrote:
> comments in line.
>
> On Sat, Mar 1, 2008 at 6:58 AM, Akinori MUSHA <knu@idaemons.org> wrote:
>
> > Hi, developers,
> >
> > After seeing Ruby 1.9.0-1 released earlier today, I, as the release
> > manager of the 1.8 series, would like to announce here that it is time
> > to start working on the next release, 1.8.7.
> >
> > Below is the timeline I made up. The reason for the slow start (long
> > period for discussion) is because I'm going on a week's trip next week
> > to Portland and Seattle.
> >
> > Schedule for 1.8.7: (subject to change as it proceeds)
> >
> > Now - 2008-03-22
> > Discuss what features should and/or can be backported, and get
> > the release manager to make decisions as to which features are
> > going to be worked on for 1.8.7.
> >
>
> In what forum are changes and features going to be discussed? ruby-core? As

Yes, ruby-core would be the best place to discuss in.

> for issues,
> see http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-core/15231
>
> Alas no comments/discussion. If you want me to work up a patch, let me know.
>
> As for back-ports, I have the honor of submitting the first tracker request
> :-)
>
> http://rubyforge.org/tracker/index.php?func=detail&aid=18517&group_id=426&atid=22040

OK, I've read the thread and the patch looks fair. But, is what you
mean by "a patch" different than is attached to the request?

--
Akinori MUSHA / http://akinori.org/

------=_Part_2464_26395784.1204582534516--