We all know how software engineering is, often we overestimate the amount of effort needed to complete a still abstract task. That's why agility prays fast, simple iterations, say no, cut the bloat. In the case of Rails, it's really more passion than deadlines involved, not to mention it is a collaborative remote effort from people around the world, the process will be kind of chaotic, in the good sense.
Now, I'm not advocating the approach the core-team uses, sometimes they go over the edge with their arrogancy, although this is changing as more people get into the 'elite' sphere (i.e getting more diverse), but I do think that this is a direct consequence of all the stupidity that you often see around a highly-hyped topic such as Rails and other IT topics. It is like selecting "friends". There are just too many people that want fast / magical results or nerds that love to troll. Marcelo. On Fri, Jul 23, 2010 at 3:48 PM, yannimac <john.mcali...@gmail.com> wrote: > Just curious, does anyone know if 3.0RC milestone in lighthouse a > correct list of the remaining bugs? I was watching it a few weeks ago > and they removed the milestone, but they added it back a few days > ago.. only 2 tickets in the milestone right now, so it looks like its > close to finished. Maybe that will give you guys a warm fuzzy feeling > about 3.0... I personally don't care what the version tag says. > > I started converting my most complex app to Rails 3 about a month ago > with the expectation that the code was almost ready based on the blog > from dhh. I was planning on pulling the trigger for the production > switchover when RC was available. But now that I have been running on > beta4, I don't see the point in waiting. My app has been tested > extensively and is running great on rails 3, and it really doesn't > matter to me what the version label is if it works. There are going > to be outstanding tickets regardless of what version they are on.. I > mean hell, 2.3.9 has 52 open tickets right now in LH. In my > experience (albeit, limited with one app on Rails 3), the code is > solid and you can figure out workarounds for any minor bug that you > might find. When RC or final 3.0 comes out I don't really expect to > have to change much (if anything). > > I understand the frustration since dhh said it would be ready in > "days" ;-) And I felt some of that frustration until I finished the > conversion and testing a few days ago. Start using Rails 3 now! You > will not regret it... there are plenty of people using it with no > problems including me. FYI.. I saw gemcutter just completed their > conversion to Rails 3. > > On Jul 23, 4:05 pm, Greg Donald <gdon...@gmail.com> wrote: >> On Thu, Jul 22, 2010 at 6:39 PM, Marnen Laibow-Koser >> >> <li...@ruby-forum.com> wrote: >> > Exactly. That's what I meant about silence being more of an issue than >> > lateness. >> >> They are in no way being silent and NOTHING is late. Take your whiny >> ass over to the dashboard and you can see EXACTLY what is going on: >> >> https://rails.lighthouseapp.com/dashboard >> >> Bunch of fucking cry-babies. geez. >> >> -- >> Greg Donald >> destiney.com | gregdonald.com > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Talk" group. > To post to this group, send email to rubyonrails-t...@googlegroups.com. > To unsubscribe from this group, send email to > rubyonrails-talk+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/rubyonrails-talk?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-t...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
