Craig: I'm with you guys. Release it...
Walt Crosby Everyday Wireless, Inc. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Craig Andera Sent: Tuesday, October 16, 2007 1:41 PM To: 'FlexWiki Users Mailing List' Subject: Re: [Flexwiki-users] I think we should ship RC0 > The > public expects V2.0 of any product to have some significant > functionality and, sorry, but security updating just doesn't sell. I agree - security is something that most won't care about. But we've got lots of other stuff in there as well, such as the features you and John have mentioned: > CAPTCHA, doc mgmt, file upload, admin, etc. are key to the wider > success of the product and, IMO, should be the first priority. I've said it before: the stuff that John, Nathan, Derek, et al. have added in the few months since the 2.0 code became stable again way trumps all the work I did in the two years before that. Which argues for a release now: judging from list traffic (really the only metric we have), far more people grab FW from the SourceForge site than from the build server. And yet we continue to recommend that people upgrade to the interim build whenever they have problems with 1.8. Now that 2.0 is to the point where it's production-quality (IMO, and for most situations), I think it makes sense to ship RC0. We're not really "shipping" so much as "moving it to a website more people look at". It's already shipped in a very real sense, as is every build we do. I tend to share John's opinion of how the dynamics of open source (as opposed to commercial) software work: that there is real value in frequent releases. Nothing says "dead project" more than "last updated 2002" on a SourceForge project page. Other reasons aside, if we value wide distribution (I don't, personally), then frequent updates are a feature. Obviously, reasonable people can disagree on this point, and whatever approach we pick will be suboptimal for someone. But as a committer, I have to say I favor frequent updates and a consciously non-commercial approach. I've said that before and I stand by it. I also want to correct one inaccuracy: > Sure, > I suppose it has a lot of significant underlying changes that make it > better (except for the fact that apparently page delivery with > WikiTalked pages is now slower - and that's going to be newsworthy). This is not actually true. Depending on what you're doing, 2.0 can actually be faster than 1.8. Indeed, in my testing against the data on www.flexwiki.com, it's significantly faster *on average*. There are some scenarios where it can be slower, but they depend on usage pattern, size of wiki, web server settings, etc. The recent discussion around performance was focusing on numbers garnered from two particular, atypically large installations of FlexWiki, with instances of somewhat sophisticated WikiTalk. The truth is that 1.8 and 2.0 are just *different* when it comes to performance, but that both deal with the common case pretty well. My hope is that the output caching in 2.2 will offer significant improvements over 2.0, putting it miles ahead of both 1.8 and 2.0 in just about every scenario, but that's completely theoretical at this point. Anyway, I just wanted to make that more clear, as I'd hate for anyone to avoid upgrading solely because they think that 2.0 is "slow" or even that it's "slower than 1.8". For simple uses that's just not true, and for more complex wikis it's...well, more complex. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Flexwiki-users mailing list Flexwiki-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flexwiki-users ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Flexwiki-users mailing list Flexwiki-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flexwiki-users
