Forum: Ruby-dev [ANN] 2.0.0 feature freeze

Japanese later; $BF|K\8l$O8e$G(B

Hi all --

Today, I'd like to declare "feature freeze" according to the schedule 
[1].
2.0.0 will NOT include any feature that is not accepted yet by matz at
this time.

[1] http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/...

Sorry for no prior announce of this.  If you, especially committers, 
have
any significant problem, please let me know by next Sunday.

In addition, I'm planning to release "feature preview" at the end of the
month.  Please tell me your opinion, ASAP.  I've heard that trunk is so
stable according to rubyci [2].  Let me know any feature that is already
accepted by matz but not implemented yet.

[2] http://rubyci.org/

We envision the first official release of 2.0 at Feb. 24, 2013, but the
concrete plan is not decided yet.  I'll announce it later on.
The possible next milestone is "code freeze".  I guess it will be near 
the
end of the year.  Be prepared.

Thanks,


$B$_$J$5$s!"(B

$BK\F|!"%9%1%8%e!<%k(B [1] $BDL$j$K(B "feature freeze" 
$B$r@k8@$7$?$$$H;W$$$^$9!#(B
$B8=;~E@$G(B matz $B$,>5Bz$7$F$J$$5!G=$O(B 2.0.0 $B$K$O4^$^$l$^$;$s!#(B

[1] http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/...

$B;vA0$KO"Mm$G$-$J$/$F$9$_$^$;$s!#$b$7=EBg$JLdBj$,$"$l$P(B 
($BFC$K%3%_%C%?$N(B
$BJ}(B) $B!"<!$NF|MKF|$^$G$K$4O"Mm$/$@$5$$!#(B

$B$^$?!"7nKv$K(B "feature preview" 
$B$r%j%j!<%9$7$?$$$H;W$C$F$$$^$9!#0U8+$,(B
$B$"$l$P$J$k$Y$/Aa$a$K$/$@$5$$!#(Brubyci [2] $B$K$h$k$H(B trunk 
$B$O7k9=0BDj$7$F(B
$B$$$k$HJ9$$$F$$$^$9!#(Bmatz 
$B$K>5G'$5$l$F$k$1$IL$<BAu$J5!G=$,$"$C$?$iO"Mm(B
$B$/$@$5$$!#(B

[2] http://rubyci.org/

2013 $BG/(B 2 $B7n(B 24 $BF|$K(B 2.0 
$B$N8x<0%j%j!<%9$rL\;X$7$F$$$^$9$,!"6qBNE*$J(B
$B%W%i%s$O7h$C$F$$$^$;$s!#8eF|O"Mm$7$^$9!#(B
$B$?$@$7!"$*$=$i$/<!$N%^%$%k%9%H!<%s$O(B "code freeze" 
$B$G$9!#G/Kv$/$i$$$K(B
$B$J$k$H;W$$$^$9$N$G!"$=$N?4$E$b$j$G$$$F$/$@$5$$!#(B

$B$h$m$7$/$*4j$$$$$?$7$^$9!#(B

2012/10/24 Yusuke Endoh <mame@tsg.ne.jp>:
> Japanese later; 日本語は後で
>
> Hi all --
>

Hello,

> Today, I'd like to declare "feature freeze" according to the schedule [1].
> 2.0.0 will NOT include any feature that is not accepted yet by matz at
> this time.
>
> [1] http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/...
>
> Sorry for no prior announce of this.  If you, especially committers, have
> any significant problem, please let me know by next Sunday.
>

There are only two things I would like be considered:

Feature #6769, Windows-specific issues with rbinstall.rb to make it
more easy generation of stub scripts.

Got initial approval of the request but my patch for it hasn't been
completed yet. I'm working on it.

Bug #7158, performance improvements to require, $LOADED_FEATURES and 
$LOAD_PATH.

I heard sometimes that Ruby policies consider performance as a feature
and not a bug, but I believe this is a valid and urgent issue that
needs to be addressed.

More and more bigger Ruby applications are developed and startup cost
on production, not to mention during development affects how we enjoy
Ruby.

Thank you.

(2012/10/24 20:53), Luis Lavena wrote:
> Bug #7158, performance improvements to require, $LOADED_FEATURES and $LOAD_PATH.

+1

Hello Luis

2012/10/24 Luis Lavena <luislavena@gmail.com>:
>> this time.
> more easy generation of stub scripts.
>
> Got initial approval of the request but my patch for it hasn't been
> completed yet. I'm working on it.

It's okay if you have already gotton approval.
Please implement it by the code freeze.


> Bug #7158, performance improvements to require, $LOADED_FEATURES and $LOAD_PATH.
>
> I heard sometimes that Ruby policies consider performance as a feature
> and not a bug,

Really?  I think a performance improvement can be accepted even after
feature freeze if it has no semantic change.
That said, in terms of stability, I hesitate to accept a big patch as
close as to the release.

I asked ko1 to judge #7158.  He will reply to that ticket within the
week.

Em 24-10-2012 09:39, Yusuke Endoh escreveu:
> Sorry for no prior announce of this.  If you, especially committers, have
> any significant problem, please let me know by next Sunday.
>
> In addition, I'm planning to release "feature preview" at the end of the
> month.  Please tell me your opinion, ASAP.  I've heard that trunk is so
> stable according to rubyci [2].  Let me know any feature that is already
> accepted by matz but not implemented yet.

https://bugs.ruby-lang.org/issues/6265
https://bugs.ruby-lang.org/issues/4840

If I remember correctly, both were accepted by none has been implemented
yet. Is that correct?

Hello Rodrigo,

#6265 was accepted.  We need a warning patch.  Will you create?

Matz has never accepted #4840, though he was indeed positive.
The discussion looks not concluded.
So 2.0.0 will NOT include that.  Sorry.


2012/10/24 Rodrigo Rosenfeld Rosas <rr.rosas@gmail.com>:

$B?\F#$G$9!#(B

In <CAJeyfuoWgCAcMt5YNwJ7y8S_HVVps4LY5hUNsqJkDMtLBOuaVw@mail.gmail.com>
  "[ruby-dev:46258] [ANN] 2.0.0 feature freeze" on Wed, 24 Oct 2012 
20:39:27 +0900,
  Yusuke Endoh <mame@tsg.ne.jp> wrote:

> $BK\F|!"%9%1%8%e!<%k(B [1] $BDL$j$K(B "feature freeze" 
$B$r@k8@$7$?$$$H;W$$$^$9!#(B
> $B8=;~E@$G(B matz $B$,>5Bz$7$F$J$$5!G=$O(B 2.0.0 $B$K$O4^$^$l$^$;$s!#(B

$B!V(Bmatz $B$,>5Bz$7!W$?5!G=$N0lMw$O$I$3$+$K$"$j$^$9$+!)$b$7$"$C(B
$B$?$i65$($F$b$i$($k$H$&$l$7$$$G$9!#(B

[ruby-core:46643]$B$K$O%5%^%j!<$,$"$j$^$7$?!#$3$N%a!<%k$r8+$k(B
$B46$8$@$H!"0lMw$O$J$/$F$=$l$>$l$N%A%1%C%H$G3NG'$7$F$M!"$H$$$&(B
$BJ70O5$$r46$8$^$7$?!#(B
  http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/...


$B;d$,5$$K$J$C$F$$$k$N$O(B
  https://bugs.ruby-lang.org/issues/5481
$B$J$s$G$9$,!"(B
  https://bugs.ruby-lang.org/issues/5481#note-28
$B$r8+$k$H(B
  Received, thank you.
$B$H=q$+$l$F$$$k$7!"(B
  https://bugs.ruby-lang.org/issues/5481#note-30
$B$r8+$k$H(B
  I did the presentation at the last dev meeting
$B$H=q$+$l$F$$$k$N$G(B[ruby-core:46643]$B$N%5%^%j!<$NCf$N$I$l$+$K(B
$B$OF~$C$F$$$k5$$,$9$k$N$G$9$,!"(B
  I guess Endoh-san didn't update this ticket yet?
$B$H$$$&$N$b$"$k$h$&$K%A%1%C%H$,99?7$5$l$F$$$J$$$h$&$G$9!#(B

$B$3$N7k2L$,$I$&$J$C$?$N$+3P$($F$$$?$i65$($F$b$i$($J$$$G$7$g$&(B
$B$+!)(B

  I/we need to clarify a part of the proposal
$B$H=q$+$l$F$$$k$N$G!"%5%^%j!<$N$&$A(B
  * 3 proposals requires feedback of proposers,
  * 3 proposals runt out of time to discuss,
$B$N$I$A$i$+$KF~$C$F$$$k$N$G$O$J$$$+$H$$$&5$$,$7$^$9$,!#!#!#(B

Em 24-10-2012 11:00, Yusuke Endoh escreveu:
> Hello Rodrigo,
>
> #6265 was accepted.  We need a warning patch.  Will you create?

I wish I was able to :) Never contributed to Ruby code before and given
my current deadlines I don't think I'll have time to work on this any
time soon. I'd probably need many days just to get started learning
about Ruby internals. Than I'd need to learn about the parser before I
could finally work on the feature itself. :(

I'd be very thankful if someone could implement it though :)

> Matz has never accepted #4840, though he was indeed positive.
> The discussion looks not concluded.
> So 2.0.0 will NOT include that.  Sorry.

No problem. From my point of view it seems like he has accepted the
feature but there are still some corner cases to be discussed before it
can be implemented :)

Thank you, Yusuke.

Hello,

On Wed, Oct 24, 2012 at 9:26 AM, Rodrigo Rosenfeld Rosas
<rr.rosas@gmail.com> wrote:
>> #6265 was accepted.  We need a warning patch.  Will you create?

Endoh-san already created such a patch I believe,
http://bugs.ruby-lang.org/issues/6265#note-9

(2012/10/24 21:44), Rodrigo Rosenfeld Rosas wrote:
>
> https://bugs.ruby-lang.org/issues/6265
> https://bugs.ruby-lang.org/issues/4840

I'm very happy if you add "title" which will helps us to remember old
memories :)

$B1sF#$G$9!#(B

2012$BG/(B10$B7n(B24$BF|(B 22:01 Kouhei Sutou <kou@cozmixng.org>:
> $B!V(Bmatz $B$,>5Bz$7!W$?5!G=$N0lMw$O$I$3$+$K$"$j$^$9$+!)$b$7$"$C(B
> $B$?$i65$($F$b$i$($k$H$&$l$7$$$G$9!#(B

$B;DG0$G$9$,;d$bM_$7$$$G$9!#(B


> [ruby-core:46643]$B$K$O%5%^%j!<$,$"$j$^$7$?!#$3$N%a!<%k$r8+$k(B
> $B46$8$@$H!"0lMw$O$J$/$F$=$l$>$l$N%A%1%C%H$G3NG'$7$F$M!"$H$$$&(B
> $BJ70O5$$r46$8$^$7$?!#(B
>   http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/...

$B$3$l$O(B 7/21 $B$N3+H/<T2q5D$G5DO@$5$l$?$b$N0lMw$G!"B>$K8DJL$K(B
$B>5G'$5$l$?$b$N$O@5D>GD0.$7$-$l$F$$$^$;$s!#(B
matz $B$,>5G'$7$?$H3NG'$G$-$k2?$+$,$"$l$P!">5G'$5$l$F$$$k$H(B
$B$_$J$9$D$b$j$G$9(B ($B6qBNE*$K$O%A%1%C%H$K$=$&=q$$$F$"$k$H$+(B) $B!#(B


> $B;d$,5$$K$J$C$F$$$k$N$O(B
>   https://bugs.ruby-lang.org/issues/5481
> $B$J$s$G$9$,!"(B
($BN,(B)
> $B$3$N7k2L$,$I$&$J$C$?$N$+3P$($F$$$?$i65$($F$b$i$($J$$$G$7$g$&(B
> $B$+!)(B

7/21 $B$N3+H/<T2q5D$G$O>5G'$5$l$F$$$^$;$s!#(BNaHi $B$5$s$,Ds0FFbMF$r(B
$B@0M}$7$F:FDs0F$7$J$*$9!"$H$$$&7kO@$K$J$C$F$$$^$9!#(B

$BDs0F<T(B (NaHi $B$5$s(B) 
$B<+?H$,2q5D$K=P@J$7$F$$$?$N$GJs9p$OG$$;$?$D$b$j(B
$B$@$C$?$N$G$9$,!"%3%_%e%K%1!<%7%g%s%(%i!<$7$?$+$b!#(B

$B;29M$^$G$KEv;~$N%a%b$rE=$C$F$*$-$^$9!#(B

NaHi $B$5$s$N<gD%(B:
  fake gem $B$O(B gem update $B$7$F$b(B (gem "json" $B$H$+$7$J$$8B$j(B)
  $B?7$7$$HG$,(B require $B$5$l$J$$LdBj$,$"$k!#(B
  $B$J$N$GI8=`%i%$%V%i%j$OIaDL$N(B gem $B$K$9$Y$-!#(B

$B7kO@(B:
  - fake gem $B$N5sF0$O%P%0$H$7$FD>$9$Y$-!#(B
    $BI8=`%i%$%V%i%j$r(B gem $B2=$9$kM}M3$K$O$J$i$J$$!#(B
  - fake gem $B$N5sF0$,D>$;$J$$(B or $BD>$9$N$KBg$-$J:$Fq$,$"$k$H(B
    $B$o$+$C$?$i!"$I$&$9$Y$-$+$^$H$a$F:FDs0F$9$k!#(B

2012/10/24 Zachary Scott <zachary@zacharyscott.net>:
> Hello,
>
> On Wed, Oct 24, 2012 at 9:26 AM, Rodrigo Rosenfeld Rosas
> <rr.rosas@gmail.com> wrote:
>>> #6265 was accepted.  We need a warning patch.  Will you create?
>
> Endoh-san already created such a patch I believe,
> http://bugs.ruby-lang.org/issues/6265#note-9

Oops, thank you for letting me know :-)

$B?\F#$G$9!#(B

In <CAJeyfup18sGOYeMUyOk8VWhLmCwmYCTiC858-X0FY_RqPSxPyQ@mail.gmail.com>
  "[ruby-dev:46260] Re: [ANN] 2.0.0 feature freeze" on Wed, 24 Oct 2012 
22:45:43 +0900,
  Yusuke Endoh <mame@tsg.ne.jp> wrote:

>> $B;d$,5$$K$J$C$F$$$k$N$O(B
>>   https://bugs.ruby-lang.org/issues/5481
>> $B$J$s$G$9$,!"(B
> ($BN,(B)
>> $B$3$N7k2L$,$I$&$J$C$?$N$+3P$($F$$$?$i65$($F$b$i$($J$$$G$7$g$&(B
>> $B$+!)(B
>
> 7/21 $B$N3+H/<T2q5D$G$O>5G'$5$l$F$$$^$;$s!#(BNaHi $B$5$s$,Ds0FFbMF$r(B
> $B@0M}$7$F:FDs0F$7$J$*$9!"$H$$$&7kO@$K$J$C$F$$$^$9!#(B

$B$o$+$j$^$7$?!#(B
$B$"$j$,$H$&$4$6$$$^$9!#(B

$B>5G'$5$l$F$$$J$$$H$$$&$3$H$G$9$,!"(B

> $B;29M$^$G$KEv;~$N%a%b$rE=$C$F$*$-$^$9!#(B

> $B7kO@(B:
>   - fake gem $B$N5sF0$O%P%0$H$7$FD>$9$Y$-!#(B
>     $BI8=`%i%$%V%i%j$r(B gem $B2=$9$kM}M3$K$O$J$i$J$$!#(B

$B$H$$$&$3$H$O$o$+$C$?$N$G$h$+$C$?$G$9!#(B

$B:#!"!V(Bfake gem $B$N5sF0!W$r!VI8=`%i%$%V%i%j$r(B gem $B2=!W$7$J$$$G(B
$BD>$=$&$H$7$F$$$k$N$G$9$,!"$=$l$,(Bcode freeze$B$^$G$K<BAu$G$-$l(B
$B$P(B2.0.0$B$KF~$l$i$l$k$H$$$&$3$H$,$o$+$j$^$7$?!#(B
$B$o$+$j$^$7$?!"$H$$$&$+!"$=$&M}2r$7$^$7$?!#(B

Em 24-10-2012 11:43, SASADA Koichi escreveu:
> (2012/10/24 21:44), Rodrigo Rosenfeld Rosas wrote:
>> https://bugs.ruby-lang.org/issues/6265
>> https://bugs.ruby-lang.org/issues/4840
> I'm very happy if you add "title" which will helps us to remember old
> memories :)

#6265 - Remove 'useless' 'concatenation' syntax
#4840 - Allow returning from require

I hope only the titles are enough for some people :) I usually don't
remember about issues just by the title, except when it was me who
created the issue ;)

Cheers

Hello!

2012/10/24 Yusuke Endoh <mame@tsg.ne.jp>:
> month.  Please tell me your opinion, ASAP.  I've heard that trunk is so
> stable according to rubyci [2].  Let me know any feature that is already
> accepted by matz but not implemented yet.

Is there a preliminary list of features new to 2.0.0? The JRuby team
would like to target Ruby 2.0 as the sole execution mode for the next
JRuby release after 1.7. We have implemented parts of 2.0, but have
not kept up with developments over the last few months.

- Charlie

2012/10/24 22:45 "Yusuke Endoh" <mame@tsg.ne.jp>:
> 7/21 $B$N3+H/<T2q5D$G$O>5G'$5$l$F$$$^$;$s!#(BNaHi $B$5$s$,Ds0FFbMF$r(B
> $B@0M}$7$F:FDs0F$7$J$*$9!"$H$$$&7kO@$K$J$C$F$$$^$9!#(B

$B$=$&$@$C$?$H;W$$$^$9!#$d$i$J$$$H$$$1$^$;$s!#(B

> $BDs0F<T(B (NaHi $B$5$s(B) $B<+?H$,2q5D$K=P@J$7$F$$$?$N$GJs9p$OG$$;$?$D$b$j(B
> $B$@$C$?$N$G$9$,!"%3%_%e%K%1!<%7%g%s%(%i!<$7$?$+$b!#(B

$B$=$N$h$&$G$9$M!#B>$K$b1sF#$5$s%5%^%j$r4|BT$7$F$k%A%1%C%H$H$+$J$$$+$J!)(B

>   - fake gem $B$N5sF0$,D>$;$J$$(B or $BD>$9$N$KBg$-$J:$Fq$,$"$k$H(B
>     $B$o$+$C$?$i!"$I$&$9$Y$-$+$^$H$a$F:FDs0F$9$k!#(B

fake gem$B$,D>$;$l$P(Bstdlib
gemify$B$O$G$-$?$bF1A3$G$9!#$H$$$&$H$A$g$C$H8lJ@$,$"$j$^$9$,!"$^$"B?$+$l>/$J$+$l7k2L$OF1$8$G$9!#EvF|$O$=$l$r<N$FBf;l$N$h$&$K8@$C$F!"$=$l$r$A$c$s$H:#8e@bL@$7$J$$$H$M!"$H$$$&$H$3$m$G;~4V@Z$l!"$@$C$?$h$&$J5$$,$7$F$-$^$7$?!#(B

$B$d$i$J$$$H$J$"!#(B

On Oct 24, 2012, at 4:39 AM, Yusuke Endoh <mame@tsg.ne.jp> wrote:
> Sorry for no prior announce of this.  If you, especially committers, have
> any significant problem, please let me know by next Sunday.
>
> In addition, I'm planning to release "feature preview" at the end of the
> month.  Please tell me your opinion, ASAP.  I've heard that trunk is so
> stable according to rubyci [2].  Let me know any feature that is already
> accepted by matz but not implemented yet.

I would like to update at least RDoc, Rake and RubyGems.  I would have 
them committed by end of November.

Is this acceptable?

2012/10/25, Charles Oliver Nutter <headius@headius.com>:
>> Sorry for no prior announce of this.  If you, especially committers, have
> not kept up with developments over the last few months.
I also want the list :-)
I expect that almost all new features are listed in trunk/NEWS,
though I've heard that some features is still missing.

2012/10/25, Eric Hodel <drbrain@segment7.net>:
>> [1] http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/...
> committed by end of November.
>
> Is this acceptable?


All right.  But please do it ASAP and minimize the change.

Note that they (and all other new features) may be rejected/reverted
if they looks disturbing the release schedule, for example, because
of delay in the development, too unstable implementation, etc.

On Wed, Oct 24, 2012 at 10:36 PM, Yusuke Endoh <mame@tsg.ne.jp> wrote:
> I also want the list :-)
> I expect that almost all new features are listed in trunk/NEWS,
> though I've heard that some features is still missing.

Ok, I will start there and monitor ruby-core for updates. Thank you!

- Charlie

I am wondering what is the status of #5481 . Although the target version 
is
3.0, there is some ongoing effort such as #6875 and [1]. So will the 
StdLib
be gemified or not? If yes, will it be done properly, i.e. all the 
bundled
libraries such as Rake, Minitest, RDoc, Psych becomes real gems, since 
the
current status is suboptimal #6124


Vit



[1] https://github.com/rubygems/rubygems/pull/377


2012/10/24 Yusuke Endoh <mame@tsg.ne.jp>

2012/10/24 Yusuke Endoh <mame@tsg.ne.jp>:

> Hi all --
>
> Today, I'd like to declare "feature freeze" according to the schedule [1].
> 2.0.0 will NOT include any feature that is not accepted yet by matz at
> this time.
>
> [1] http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/...
>
> Sorry for no prior announce of this.  If you, especially committers, have
> any significant problem, please let me know by next Sunday.

Hello Yusuke

Does that apply to the stdlib too? Or is it just for the core? What
about the proposal to gemify the stdlib?

I've raised the following feature request quite some time ago

https://bugs.ruby-lang.org/issues/4569

but nothing has been done so far, I haven't received any feedback, and
now this 2.0 feature freeze announcement comes out of the blue (for me
at least).

Hello,

2012/10/25, Vit Ondruch <v.ondruch@gmail.com>:
> I am wondering what is the status of #5481 . Although the target version is
> 3.0, there is some ongoing effort such as #6875 and [1]. So will the StdLib
> be gemified or not?

The short answer is "no."

We discussed #5481 at the developers' meeting (Jul. 21), and
it was not accepted.  I'll add the brief log to that ticket.

Hello Marco,

2012/10/25, Marco Ceresa <ceresa@gmail.com>:
> Does that apply to the stdlib too?

Yes, in principle.


> What about the proposal to gemify the stdlib?

See my reply in #5481 and wait for NaHi.


> I've raised the following feature request quite some time ago
>
> https://bugs.ruby-lang.org/issues/4569
>
> but nothing has been done so far, I haven't received any feedback, and
> now this 2.0 feature freeze announcement comes out of the blue (for me
> at least).

Sorry, but please do NOT assume that you can get a feedback
just by opening a feature request ticket.
All feature proposers are supposed to make an effort to get
related committers' interest and matz's approval.
You can exploit the opportunity such as [ruby-core:45474].
It is also a very good idea to appeal to matz face-to-face,
e.g., at some conferences.

(Note that this does not apply to bug report ticket.  The
committers must check and fix them.)

In short, you don't have to hesitate, or even you are
encouraged to open any feature request ticket, but it is
often insufficient.

On Thu, Oct 25, 2012 at 2:14 PM, Yusuke Endoh <mame@tsg.ne.jp> wrote:

>> but nothing has been done so far, I haven't received any feedback, and
>> now this 2.0 feature freeze announcement comes out of the blue (for me
>> at least).
>
> Sorry, but please do NOT assume that you can get a feedback
> just by opening a feature request ticket.
> All feature proposers are supposed to make an effort to get
> related committers' interest and matz's approval.

Thanks for your answer and your advices Yusuke.

I have written to mr. Knu (maintainer of IPAddr) multiple times, I
have interacted with Matz which was positive about the idea, I have
opened the ticket and even asked what I could do to help.

Next step was to be reported for stalking, but I have a family to take
care of and they don't let me code from prison :-)

> It is also a very good idea to appeal to matz face-to-face,
> e.g., at some conferences.

I've tried with a horse head in the bed, didn't work.

> In short, you don't have to hesitate, or even you are
> encouraged to open any feature request ticket, but it is
> often insufficient.

Got the message. I'll have to improve my determination from this point
of view. Thanks again for your adivces.

Now, my 2 cents: IPAddr should not be part of Ruby 2.0. It is too
outdated and too strangely behaving to be the default IP addresses
management library for a mainstream language such as Ruby. I know Ruby
doesn't exactly target to networking, but If you don't plan to replace
it with some other library (there are many) at least consider to just
not include it.

Hi,

In cgi.rb,
I think HTML5 tag generater will be include in 2.0

https://bugs.ruby-lang.org/issues/6637

I will commit to update include this ticket while few days.

Hi,

I checked all "not closed" features.

https://bugs.ruby-lang.org/projects/ruby-trunk/iss...

and I send notice with

- add comment (ping) on redmine
- assign to mame-san on redmine the ticket which I can't judge
- change target to next minor when it seems no discussion on it
- twitter to people who check twitter frequently
- skype to nobu
- IRC to nurse-san
- mail (akr-san and matz)

Please correct me if my changes are not correct.

Note that ~assigned to Matz" is almost equivalent to "ignored".
I think you need to make pressure to Matz (with good explanation, good
usecase, etc).

Thanks,
Koichi

I found that there are 183 not-closed features which are not specified
target version...

https://bugs.ruby-lang.org/projects/ruby-trunk/iss...

I didn't check it.  Please set target version if you strongly believe it
should be introduce into 2.0.

Thanks,
Koichi

Hello,

2012年10月24日 20:39 Yusuke Endoh <mame@tsg.ne.jp>:
> Let me know any feature that is already
> accepted by matz but not implemented yet.
>
As far as I'm concerned, these two tickets match the condition.

* Feature #6670: str.chars.last should be possible
* Feature #3346: __DIR__ revisted

(2012/10/24 5:39), Yusuke Endoh wrote:
> Sorry for no prior announce of this.  If you, especially committers, have
> any significant problem, please let me know by next Sunday.

I will consider/chanabout the following 10 tickets.

http://bugs.ruby-lang.org/projects/ruby-trunk/issu...

Sorry for my late response.

Hello ko1,

2012/11/1 SASADA Koichi <ko1@atdot.net>:
> (2012/10/24 5:39), Yusuke Endoh wrote:
>> Sorry for no prior announce of this.  If you, especially committers, have
>> any significant problem, please let me know by next Sunday.
>
> I will consider/chanabout the following 10 tickets.

Thank you.

- I think that #6895, #7051, and #6762 are too heavy to include in 2.0.
  I'm reluctant.

- Did matz accepted the parameter setting features by environment 
variables
  (#4614 and #3187)?

- Matz looks negative to #6710.

- Adding only a document is okay.  (#3731)

- #1586 is already accepted.

- #2294 and #1952 looks okay, but please hurry to implement.
  If they prevent the release engineering, I will defer them to next 
minor.

I recognize #3731, #1586, #2294 and #1952 are accepted but unimplemented
2.0 features.

Hi,

How about #6636?

AFAIK matz has not accepted #6636 completely yet.

2012/11/2 Marc-Andre Lafortune <ruby-core-mailing-list@marc-andre.ca>:

Sorry, late to the party, but what's the status of #6679?

What status of #6638 <https://bugs.ruby-lang.org/issues/6638>

2012/11/3 Clay Trump <clay.trump@gmail.com>

2012/11/3 Clay Trump <clay.trump@gmail.com>:
> Sorry, late to the party, but what's the status of #6679?

#6679 is already accepted, and is on the waiting for Naruse's 
implementation.
But if it is implemented by code freeze at the latest, I must postpone
that to Next Major.

2012/11/3   <funny.falcon@gmail.com>:
> What status of #6638

Up to nobu.
But my personal opinion is that it may be difficult to include that in
2.0.0.  Sorry.

> 2012/11/3 Юрий Соколов <funny.falcon@gmail.com>:
> > What status of #6638
>
> Up to nobu.
> But my personal opinion is that it may be difficult to include that in
> 2.0.0.  Sorry.

Endoh-san, why (specifically) do you believe the patch would be 
difficult to include in 2.0.0?

I assume you're OK with patch application mechanics, but have concerns 
about something else?

Jon

2012/11/4 Jon <jon.forums@gmail.com>:
>> 2012/11/3   <funny.falcon@gmail.com>:
>> > What status of #6638
>>
>> Up to nobu.
>> But my personal opinion is that it may be difficult to include that in
>> 2.0.0.  Sorry.
>
> Endoh-san, why (specifically) do you believe the patch would be difficult to 
include in 2.0.0?

Just because it is technically advanced and not well-tested yet.
It often makes debugging hard for us to complicate basic data invariant.

But I'm not against if nobu applies the patch and if it causes no 
problem.
So press him to review and commit the patch.

> Just because it is technically advanced and not well-tested yet.
> It often makes debugging hard for us to complicate basic data invariant.
>
> But I'm not against if nobu applies the patch and if it causes no problem.
> So press him to review and commit the patch.


Understood. I just posted successful `make test` and `make test-all` 
results on trunk@37463 using win7 32bit and mingw-w64 gcc 4.7.2 and will 
try on my arch 3.6.5 vm w/4.7.2 when I see an updated trunk pushed to 
the github mirror. And if I'm feeling particularly flush with free time 
I may try it on my snow leopard vm.

nobu-san...any specific concerns or additional tests you'd like to see 
that are not already covered by trunk's test suite?

Jon

---
Fail fast. Fail often. Fail publicly. Learn. Adapt. Repeat.
http://thecodeshop.github.com | http://jonforums.github.com/
twitter: @jonforums