OK with that plan. Wed noon PST time, I will cut a last RC (with just one change), and we will vote on it then.
On Mon, Jun 14, 2010 at 11:53, Daniel Spiewak <[email protected]> wrote: > I vote we wait 48 hours (or preferably less) for people to get in any > last-minute reports. If we don't hear about anything devastating (and by > "devastating", I mean "end of the world") by then, I vote we cut the release > and move on to any remaining issues in an update. > > The point has been raised that our current "stable" release is unusable due > to issues with rubygems. This is a pretty critical bug, and I think it's > important that we don't lose sight of that fact as we try to squash any > remaining issues in 1.4. Just my two cents. > > Daniel > > > On Mon, Jun 14, 2010 at 1:44 PM, Antoine Toulme > <[email protected]>wrote: > >> Buildr devs, >> >> my week-end consisted of looking into ODE to make it work well with the >> latest release. >> It turns out ODE uses the Hibernate task and specializes it in an invalid >> way. >> I committed changes that will fix the issue durably. >> >> There were no problem in the core files themselves. >> >> I spent Sunday installing Rubinius (it's all installed now, but we run >> into >> issues when running rake -S spec). This is a low priority, not so >> impacting >> work. >> >> How do we take it forward ? Should I cut a new RC ? Should we wait 48h >> hours >> for people to report ? >> >> Thanks, >> >> Antoine >> > >
