Crispy wrote
I am not sure what you guys want. Would you rather have a release that had bugs, or wait a couple extra days? It was fully my intent to have this release available as of two days ago, but because of last minute bugs this was not possible. I put tons of time into the module as a volunteer and I have to wait for other volunteers as well to do things properly. There is nothing more discouraging than to come in here and read half the crap you guys write.
|
Don't be discouraged. If anything you should be proud that so many want the results of your long hours of volunteering.
As far as having a release that had bugs or a waiting... personally I'd rather have the release. This board has been running updated code for almost 2 months that fix alot of the issues I have in the current build. (Fact is the currently published version is "unusable" as deemed by my end users.) So even if you had published the code from a month ago, I would have been happy to put up with the bugs to get the ones that I did have fixed. No software of any complexity is ever "bug" free.
DNN decided long ago to go the "closed source until release" route, that comes with the price of people wanting to get the latest fixes... and being unable too, thus frustration. Frustration on both ends, the developers end by thinking the community doesn't appreciate their efforts and the users that are frustrated by timelines that don't seem to ever stick. (For one reason or another.) DNN and its sub-projects are great, the developers of them are great. Hopefully you can see the logic of why I would think its funny that "yet another" timeline passes un-fullfilled. And honestly I do think its "funny". Sorry if that humor offends, as its not intended.