Hi, On 2005/06/29, at 17:14, Adeodato Simó wrote: > Well, the idea (sorry if I didn't explain myself properly) was not to > ship ruby1.9 in any Debian stable release, not only Sarge. For this, > the bug would have to be kept open even after releasing Sarge, > otherwise the package will migrate to testing and would get released > with Etch. > > OTOH, I can understand that you'd like to see ruby1.9 in testing, at > least during the development cycle of Etch. If this is the case (i.e., > you prefer ruby1.9 to be both in testing and in unstable, instead of > only in unstable), we could arrange something. For example, letting it > in and make sure we remove it before relesaing. I must say I don't > like this idea very much, but can be a compromise. What do you think?
I wish to include ruby1.9 into Etch. Some reasons are: * On some parts, ruby1.9 is different from ruby1.8. * Some programs requires ruby1.9. (ex: Ruby support of Gonzui) I think that ruby1.9 does not annoy users because users can know that ruby1.9 is development version of Ruby. And if ruby1.9 is not suitable to release with Etch then ruby1.9 must have RC-bugs which is not a dummy report. Thank you. -- akira yamada
