Quote:
Originally posted by andrew67
Thanks & Gratitute go along way in this world. Woopee I made a mistake, you must never make mistakes, you are so perfect... Frigg this, I am removing this hack, I will release it to a more gratefull bunch of people.
|
Andrew... allow me to be the voice of reason: Many of us were happy to see an EIRC integration hack come onto the scene and many of us don't see it as necessarily being a life and death issue if the hack doesn't work perfectly right out of the box.
However, the proper order of things
is to place a new hack in Beta before you announce it as a full release. Even if the hack works flawlessly on your site, it is wise to put it into beta for a few days just to work out any kinks that may arise.
In this case, you obviously had to go back and re-address some issues with the documentation. Not a big deal, but there are always going to be people who want to bust your balls about this sort of thing. Having put this into beta would have given you that opportunity to work the kinks out with the users understanding that there
might be problems in the release.
Putting a hack into beta before you release it to the public is just a smart practice to adhere to and, if done, gives you a basis to tell people to STFU whenever the whining begins.
So don't let a few complaints spoil this for you. Keep releasing your work knowing that there
are people who appreciate it, but follow through with a beta cycle first.