Hello guys,
I went into milestones page (Upcoming Milestones - Ruby on Rails - rails) and found out that Rails 2.3.6 was due Jan 15, 2010. Does it mean all tickets in that milestone should be cleared first?
If so, then I would pay attention to clear tickets in that bucket first.
Thank you,
Prem Sichanugrist (sikachu)
I'd like to reraise this question. The Lighthouse milestone page still shows a date of January 15, but now it's 2 months after. There's almost 4 months worth of stable, relevant fixes ready to go for a 2.3.6 release, including critical fixes for SMTP and fixes the use of Rubygems APIs that were deprecated in the Feb 20 Rugygem release that will be removed on or after August 2010.
We're also looking forward to a stored procedure compatibility fix that's in the 2-3-stable branch as well.
What's the plan?
We're also looking forward to a stored procedure compatibility fix that's in the 2-3-stable branch as well.
What's the plan?
Apologies for the lack of communication on this. Professional Life and Family Life combined and resulted in no free time for me to work on rails.
On my plate prior to 2.3.6 is tidying up 2-3-stable's XSS changes to ensure backwards compatibility with 2.3.5 and the rails/rails_xss plugin. Once that's done then I'll do a pass through lighthouse and here looking for things which should block a release. After that, hopefully we can settle down into a six-weekly point release cycle.
My hunch is that 2.3.6 will land more like 'early april' than 'late march' but it's not far off. Apologies again for the delay.
Hey guys,
any update on the release date for 2.3.6?
Cheers, Szymon