Feature #2635: Unbundle rdoc

• Status: Rejected
• Assignee: matz (Yukihiro Matsumoto)
• Target version: 1.9.2

[naruse (Yui NARUSE)]

=begin
The rdoc in trunk is outdated and not maintained,
and latest rdoc is in gen.

I think Ruby 1.9 shouldn't bundle such old rdoc.
People who needs rdoc should install from gem.
=end

[matz (Yukihiro Matsumoto)]

=begin
Hi,

In message "Re: [ruby-core:27722] [Feature #2635] Unbundle rdoc"
on Sat, 23 Jan 2010 23:20:59 +0900, Yui NARUSE [e-mail] writes:

|The rdoc in trunk is outdated and not maintained,
|and latest rdoc is in gen.
|
|I think Ruby 1.9 shouldn't bundle such old rdoc.
|People who needs rdoc should install from gem.

Or bundle newer rdoc?

						matz.

=end

[naruse (Yui NARUSE)]

=begin
Bug #2066 is written by Run Paint Run Run 136 days ago, but it is not yet.

Moreover rdoc has some open bugs for 1 year.
test-all failure and crash bugs need to fixed but not fixed.
I, maintaining Redmine's tickets, hate those unmaintained libraries.
=end

[matz (Yukihiro Matsumoto)]

=begin
Hi,

In message "Re: [ruby-core:27725] [Feature #2635] Unbundle rdoc"
on Sun, 24 Jan 2010 00:15:33 +0900, Yui NARUSE [e-mail] writes:

|Moreover rdoc has some open bugs for 1 year.
|test-all failure and crash bugs need to fixed but not fixed.
|I, maintaining Redmine's tickets, hate those unmaintained libraries.

In that case, should we ask for new volunteer instead of removing it?

						matz.

=end

[luislavena (Luis Lavena)]

=begin
On Sat, Jan 23, 2010 at 12:15 PM, Yui NARUSE [e-mail] wrote:

Moreover rdoc has some open bugs for 1 year.
test-all failure and crash bugs need to fixed but not fixed.
I, maintaining Redmine's tickets, hate those unmaintained libraries.

Is my understanding that rdoc has been updated and maintained by Eric
Hodel, at least eh gem was.

If integration with Ruby is the problem, then removal and optional
installation for the user should be the solution, right?

Luis Lavena
AREA 17

Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exupéry

=end

[naruse (Yui NARUSE)]

=begin
(2010/01/24 0:35), Yukihiro Matsumoto wrote:

|Moreover rdoc has some open bugs for 1 year.
|test-all failure and crash bugs need to fixed but not fixed.
|I, maintaining Redmine's tickets, hate those unmaintained libraries.

In that case, should we ask for new volunteer instead of removing it?

If someone maintain rdoc lib in Ruby, it is clear.

--
NARUSE, Yui [e-mail]

=end

[matz (Yukihiro Matsumoto)]

=begin
Hi,

In message "Re: [ruby-core:27729] Re: [Feature #2635] Unbundle rdoc"
on Sun, 24 Jan 2010 00:41:18 +0900, Luis Lavena [e-mail] writes:

|Is my understanding that rdoc has been updated and maintained by Eric
|Hodel, at least eh gem was.
|
|If integration with Ruby is the problem, then removal and optional
|installation for the user should be the solution, right?

That's what I don't understand. Eric has commit privilege. If he
still maintains rdoc gem, I see no reason he doesn't update the
bundled rdoc as well. If he stops maintaining rdoc, we need new
maintainer. If he keeps working on it, I expect him to update bundled
rdoc as well.

						matz.

=end

[naruse (Yui NARUSE)]

=begin
(2010/01/24 0:41), Luis Lavena wrote:

On Sat, Jan 23, 2010 at 12:15 PM, Yui NARUSE [e-mail] wrote:

Moreover rdoc has some open bugs for 1 year.
test-all failure and crash bugs need to fixed but not fixed.
I, maintaining Redmine's tickets, hate those unmaintained libraries.

Is my understanding that rdoc has been updated and maintained by Eric
Hodel, at least eh gem was.

I think so too.

If integration with Ruby is the problem, then removal and optional
installation for the user should be the solution, right?

Yeah, I think so.
rdoc is pure ruby, so it won't be a severe problem,
even if Ruby's installation process needs some changes.

--
NARUSE, Yui [e-mail]

=end

[mame (Yusuke Endoh)]

=begin
Hi,

2010/1/23 Yukihiro Matsumoto [e-mail]:

In message "Re: [ruby-core:27722] [Feature #2635] Unbundle rdoc"
on Sat, 23 Jan 2010 23:20:59 +0900, Yui NARUSE [e-mail] writes:

|The rdoc in trunk is outdated and not maintained,
|and latest rdoc is in gen.
|
|I think Ruby 1.9 shouldn't bundle such old rdoc.
|People who needs rdoc should install from gem.

Or bundle newer rdoc?

I don't know much about the "latest" rdoc, but according to [ruby-core:27667],
I understand that simply updating causes compatibility problem because:

The latest RDoc no longer has the HTML generator at all.

The reporter in [ruby-core:27656] followed proper reporting procedure (i.e.,
tested and patched against 1.9 trunk). Ruby's development process is wrong.
It is too confusing for rdoc to have independent trunk.
In [ruby-core:27667],

I fixed this memory issue by deleting the file.

is equal to "I fixed in my own envirionment!" It does not answer.

I wonder why some standard libraries (RubyGems, Rake, rdoc, etc.) need
to have independent development process and independent release.
I said in [ruby-core:26679], they should be developed and released with
ruby core if they are really parts of ruby core.

--
Yusuke ENDOH [e-mail]

=end

[zenspider (Ryan Davis)]

=begin

On Jan 23, 2010, at 19:03 , Yusuke ENDOH wrote:

The reporter in [ruby-core:27656] followed proper reporting procedure (i.e.,
tested and patched against 1.9 trunk). Ruby's development process is wrong.
It is too confusing for rdoc to have independent trunk.

Then we should eject ALL of standard lib from trunk. Gemify all of them and kick them out the door.

Maybe we should bundle some gems, but they should install as actual gems and be freely upgradable by the user.

Like it or not, rdoc, minitest (and test/unit), rubygems, rexml, and yaml (and others?) are all separate products that are produced independent of trunk. In my opinion, it works BETTER that way, not worse. What doesn't work is having to slow down releases because ruby releases are so few and far between.

=end

[jbarnette (John Barnette)]

=begin
On Sun, Jan 24, 2010 at 10:31 PM, Ryan Davis [e-mail] wrote:

Like it or not, rdoc, minitest (and test/unit), rubygems, rexml, and yaml (and others?) are all separate products that are produced independent of trunk. In my opinion, it works BETTER that way, not worse. What doesn't work is having to slow down releases because ruby releases are so few and far between.

Rake. Rex. Racc.

~ j.

=end

[naruse (Yui NARUSE)]

=begin
On Mon, Jan 25, 2010 at 3:31 PM, Ryan Davis [e-mail] wrote:

On Jan 23, 2010, at 19:03 , Yusuke ENDOH wrote:

The reporter in [ruby-core:27656] followed proper reporting procedure (i.e.,
tested and patched against 1.9 trunk).  Ruby's development process is wrong.
It is too confusing for rdoc to have independent trunk.

Then we should eject ALL of standard lib from trunk. Gemify all of them and kick them out the door.

Maybe we should bundle some gems, but they should install as actual gems and be freely upgradable by the user.

Like it or not, rdoc, minitest (and test/unit), rubygems, rexml, and yaml (and others?) are all separate products that are produced independent of trunk. In my opinion, it works BETTER that way, not worse. What doesn't work is having to slow down releases because ruby releases are so few and far between.

I don't think it is a problem that some libraries are developed out of
Ruby's repos,
until the maintainer fixes bugs created in Ruby's Redmine and update
the lib in trunk.
Current minitest, nkf, JSON, is doing that. (I maintain nkf and JSON)
REXML, YAML, racc are note developed.
rake doesn't but not have reported bugs.

--
NARUSE, Yui
[e-mail]

=end

[mame (Yusuke Endoh)]

=begin
Hi,

2010/1/25 Ryan Davis [e-mail]:

On Jan 23, 2010, at 19:03 , Yusuke ENDOH wrote:

The reporter in [ruby-core:27656] followed proper reporting procedure (i.e.,
tested and patched against 1.9 trunk). Ruby's development process is wrong.
It is too confusing for rdoc to have independent trunk.

In my opinion, it works BETTER that way, not worse.

It brings some benefits, but problems actually occur.

• slow synchronization between the "latest" and ruby trunk
• empty answer that the issue is fixed in the "latest"
• neglect of tickets in ruby's redmine
• incompatible change to the "latest"

These problems do not occur or are detected early if they
are developed in ruby trunk. Nobody would say anything if
such a problem does not occur, I think.

--
Yusuke ENDOH [e-mail]

=end

[naruse (Yui NARUSE)]

• Status changed from Assigned to Rejected

=begin

=end

[hsbt (Hiroshi SHIBATA)]

• Related to Feature #5481: Gemifying Ruby standard library added