[Ruby2c] Re: [ ruby2c-Bugs-1422 ] \n in a Ruby string ends up as a literal newline in C code

[Paul]

Pat beat me to it but I'd have to agree. See what other bugs you can
close in a week, then release a point release with the CHANGELOG.

I'd say the only time a point release should come out so soon is if
there is a severe security issue that needs to be patched ASAP.

My $0.02



On Thu, 3 Feb 2005 11:49:28 -0800, pat eyler <pat.eyler at gmail.com> wrote:
> On Thu, 3 Feb 2005 11:24:59 -0800, Ryan Davis <ryand-ruby at zenspider.com> wrote:
> >
> > On Feb 1, 2005, at 9:54 PM, noreply at rubyforge.org wrote:
> 
> > I fixed this and submitted to perforce. I hesitate marking the bug
> > closed until it is released, but I also hesitate doing a point release
> > the day after the beta release. Since rubyforge doesn't have but 3
> > different states for the bug, I can't do much but add a comment. How do
> > you guys suggest we handle this?
> >
> 
> I'd say mark it closed, and make this part of a point release in a week or
> (along with all the other bugs that surface and get whacked by that point).
> 
> --
> thanks,
> -pate
> -------------------------
> ParseTree is a little brown stinky ferret that digs down a hole and
> violently rips the
> AST away from the warm bosom of ruby. In other words, we cheat, they
> don't.
> _______________________________________________
> ruby2c mailing list
> ruby2c at zenspider.com
> http://www.zenspider.com/mailman/listinfo/ruby2c
>