|
When releaseing vB3 hacks
Stop useing ++++ty untested code.
vB3 code is nice and clean and thats how you should do hack. RC has been out for a few days and theres a ton of FULL RELEASES then you read the threads and people point out 100 bugs. Don't rush to be the first one to release hacks. Like I have my Clan Tools hack that I have been working on for months now as some may know and it's being tested on 5 boards right now, I was gonna release it but why go through the trouble of putting a crappy code out. Please test you code and clean it up. Also since everyone is re-releaseing the "popular hacks" give the orignal author credit. And thats my 2 cents on you people who do what I just said. |
I still say don't hack at all because you're just destroying a stable product, but that didn't deter people from it during the beta and gamma stages.
|
a stable product is good, but a less-stable product with hundreds of new features that attract members is better :p
but I agree, I downloaded a bunch of the hacks for vB3 so that I am able to use them later on, only to hear a little on that there's this error here and that bug there.... either test out your hack completely or release it in the BETA forum for testing but im not arguing, more hacks = sweeter features.... as long as the hack doesnt destroy my board :p MGM out |
Personally I don't install hacks for any bbs without waiting like a week to see if the hack is stable or not.
Dark Shogun |
I'm waitin for Gold as they say it will take less time then Gamma to RC if no big problems arise.
|
Man, have I been absent lately.
vBulletin 3 RC (and RC2?) released? Tons of vB3 hacks? Looks like I need to get on the road. :^| |
IMO, another RC means just one step closer to Final.
I put more trust into the vBulletin developers whenever they released another Beta, the Gamma, or another RC. It means they're doing their job in releasing a close to bug-less system. :) Some people fail to realize that though... |
vB3 has ONE unconfirmed bug left. We might be lookin at final pretty damn soon.
|
I say all hacks should be submitted for moderation by xenon himself before they get released.
|
Quote:
I say possibly 1-2 weeks after that bug is fixed. :) Quote:
|
Quote:
|
A safety precaution of installing hacks, is to always make a complete backup, and of course for members who choose to, install it on a test forum. I agree though, that some of the hacks being released do need some more testing before the release, but obviously some people don't feel the same way.
|
Quote:
i perosonally run hacks on my own site / test site / and let a few others test it first before letting it out to the public. my coding for what ive currently released is rather solid i belive and you should look into some of the hacks coding before you go around calling all ++++ty untested code :) i learnd howto hack on vB3 there for most of my coding should represent vB3's coding standards, well to the best of my abilties anyway |
Quote:
Don't expect me to spend hours tidying up code for other people - as long as the code is secure, optimized and works, I'll release it. Feel free to modify it for your own site. :) One reason why I've had to change some of my first releases is because some code still had bits from my site in it. :) But those are easily changed. |
Quote:
|
I don't see him say ALL vB3 hacks have messed up code.
Dark Shogun |
Quote:
its your own fault if you dont check the code first |
Quote:
|
Quote:
|
Quote:
Besides, there is a QA system still being implemented... right? :rolleyes: |
*cough* https://vborg.vbsupport.ru/showthread.php?t=58192 *Cough*
|
Quote:
|
The Quality Assurance System will be implemented. The details are being discussed. We're trying to find a balance between regulating hack releases vs. overcontrolling hack authors.
|
Quote:
|
Madcatt - somehow I don't think Stefan has the time to go through and moderate every hack. This is where the QA system will come in sometime soon.
|
Even if Xenon did have time to check each hack, it still doesn't ensure quality. Having only one person look at it (and when its one person that looks at all of them) IMO isn't likly to ensure quality at all. Everyone makes mistakes and if one person is resonsible for checking each and every vB3 hack then I feel alot of mistakes would be made, no matter who did it.
Why do you think vB3 had a public beta? Do you think they would have found and fixed all the bugs the have if it was just the vB devs checking it? I don't. |
Remember, different people have different definitions of what is "quality". For some, how the code looks is important. To others, how the code look does not matter at all, as long as it is secure, and optimized. It's all a matter of different people having different tastes.
|
| All times are GMT. The time now is 02:08 PM. |
Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.
| X vBulletin 3.8.12 by vBS Debug Information | |
|---|---|
|
|
 More Information |
|
|
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|