3 ms·
That's a very polite way to put it, imo. These same people demanding an immediate release would also be the first to weep prose all over the internets upon the
by mahmud 16y ago
That's a very polite way to put it, imo. These same people demanding an immediate release would also be the first to weep prose all over the internets upon the first contact with a bug.
- tghw 16y agoNo one was demanding an immediate release. They were just asking for some form of communication. Their expectations were set for a release back in June. That date came and went without any information. A month and a half later, it takes someone asking about it just to get "real soon" as a reply. Go take a look at how Django handles this: http://www.djangoproject.com/weblog/ http://www.djangoproject.com/weblog/. For the 1.2 release, they posted every week with a detailed update of when they thought the RC would drop, what bugs were holding it back, and what areas needed the most help. Each week, you could see them getting closer, and when they got delayed, you understood why.
- mahmud 16y agoIf I used Rails and had to put up with a release cycle that didn't meet my expectations, you can be sure I would fork it. The bunch of people in that thread can organize themselves and get intimate with the source tree (or switch to something else.)