Hugh Sasse Staff Elec Eng <hgs / dmu.ac.uk> writes:

> How would a new user know: 
> (a) where to look for this patch
> (c) to what extent it had been tried and tested
> (c) whether such a patch had been accepted and integrated into Ruby
> (d) whether there were patches that obsolete this patch?
> 
> Should we not have ruby-1.6.1.X so that people can know where they are
> with patches?  Is this a lot more work?  Would there be an impact on
> 1.6.2 development, or even 1.7.x development?  Would such a scheme to
> too inflexible for our needs?

All these patches are rolled in to the source tree, and are available
via either CVS or using the daily tarball.

The missing piece is the notification system: there is a Ruby bug
tracking system at http://www.ruby-lang.org/cgi-bin/ruby-bugs, but
people tend not to use it. If the solaris issue was raised as a bug
report, rather than as a message to the list, then Matz would have
posted a response back to that system. Anyone looking for help with a
Solaris issue would then go to the system and find it.

If we could make use of this system more universal, then its value
would increase dramatically.


Dave