SMF 2.0.18 has been released! Please update. Read more.
Started by [SiNaN], May 05, 2011, 07:08:48 PM
Quote from: searchgr on June 07, 2011, 02:24:11 PMLet's wait for the Windows 8 first ....
Quote from: IchBin™ on June 07, 2011, 04:05:41 PM
Quote from: sharks on June 07, 2011, 11:51:54 AMThis looks like a new episode in the infamous reality series "SMF team fights and quits". Damn... 2.0 final looks very far away all of a sudden. *deep sigh*
Quote from: Antechinus on June 07, 2011, 06:21:45 PMNot really. Motoko isn't on the team and hasn't been for ages. His grumbling doesn't affect anything.
Quote from: 青山 素子 on June 07, 2011, 06:46:11 PMQuote from: Antechinus on June 07, 2011, 06:21:45 PMNot really. Motoko isn't on the team and hasn't been for ages. His grumbling doesn't affect anything.Indeed. That, however, doesn't mean I can't snark a little. I mean, the OpenID bug that was all of a sudden a stopper had been present for many many months. It's interesting that it was so suddenly considered a blocker to 2.0 rather than a major or medium-priority bug for a 2.0.1 release. I mean, that's happened in the past. You're not going to get any kind of complex software completely bug-free. Instead of delaying until it's "prefect", just release once all the crucial things (data loss bugs, for instance) are done and make a few bugfix updates later.It's been how long since the NPO has fully owned the software? I recall when the public was being told that the transfer was the only thing holding up the release and pointing fingers about signatures and other stuff. I also recall a few of the developers simply stopping coding because they didn't want to work on a project that might become "dead". (not sure if that exact word was used, but that was implied for sure...)Why not just have gone for the truth with a simple "We're not quite comfortable releasing it in the current state" rather than blaming outside forces? I guess that wouldn't go because then the current team would have had to take responsibility for any further delays instead of conveniently blaming the problem-du-jour.I am very glad to see the current team start owning up to some of the delay that has occurred now that there is nobody/nothing to blame, I just wish that had started sooner as owning the problem leads to action to resolve it (for better or worse).
Quote from: live627 on June 07, 2011, 07:29:32 PMWhat's wrong with some online novels, to loosely paraphrase a team member here?
Quote from: Antechinus on June 07, 2011, 07:37:55 PMI wandered as a beggar(snip)