My only problem with the response is that it came across as 'why dont you check your work and make sure ALL errors are corrected before you post something'
Drawde specifically mentioned, as I did that there were a couple of bugs, but other than that it worked great....
The problem seems to be that the wrong db.sql is being used.
Its really not his job to go and put everything together for you and make a full release, if you want to use his BETA database, then you should go to CVS on sourceforge and download the latest db.sql file, rather than complaining about the one he provided. CVS is freely available to everyone, so use it. Otherwise, we'll just cut CVS updates off completely, and not make anything available until a stable version is released so we dont have people whining about not being able to attatch an updated part A to an updated part B because they expect everything to be done for them. When I set up the Sourceforge CVS updates, thats exactly what I was afraid of in the 1st place.
As Drawde notes in his version, it's beta, and no offense, but he's been releasing them for well over a year now, and has always done a smash up job, so the 'why dont you test it' tone kind of got under my skin'
He did offer to help fix the errors in a later post, which I think would have been more apprioate in the first post. Messages of this sort are appreciated..
'Hey, noticed a bug, you need to modify X to Y and that will correct it, in fact, I modified it and pasted it here !'
as opposed to
'Hey, noticed a bug.. We dont you fix these things before you release them?'
Like I said, I'm sure that's not what was meant, but the tone of the message came across as rude.
__________________
Quitters never win, and winners never quit, but those who never win and never quit are idiots.
|