He meant no hacks for the vB 3.5 Betas will be allowed to be released here - the same policy that was used for vB3 until Release Candidate 1. Then again, Zachery is probably just guessing.

I just don't understand all these questions about whether and when the porting of hacks will be. ( not re:WhSox21's first post though )
3.5 isn't even in any released beta stage yet. None of us less the developers and a priviledged few have seen the code. So why bother speculating now ? :)

And in reply to WhSox21's question, I'm sure vb.org will soon have a 3.5 section as well, to better organize hacks, since codebase has changed somewhat and not all hacks ( and users themselves ) may be ready to move to 3.5 compliant coding standards. We'll just have to wait and see, won't we :)

I am sure they will ONCE IT IS OUT OF BETA. Considering the BETA hasnt even been released yet, we will all jsut have to wait.


I fail to see that.

Well that still seems daft to me.

Isn't this why vb.org has a beta hacks forum ? - how can you get people to test hacks for 3.5 if you can't release them. Crazy.

The beta forum is for coders to release hacks that are not yet 'ready', it does not refer to vBulletin beta releases.

When 3.0.0 was in beta we did not allow hacks to be posted for version 3 here, I asume we will do the same for 3.5 but that is not set in stone.

Once we see what 3.5 is really all about we will alter things as needed.

Yes I realised that - what I mean is that if the vB version is beta, then any hacks for it must also be considered as beta. :)

So I heard, and I still don't understand the reasoning for this.

I certainly hope not.

Good.

Letting users hack their beta boards only causes problems(as in releasing hacks here, ect). I cannot remember how many times people posting on vB.org for vB3 beta support were having problems (above and beyond normal) because of hacking.

In my response to the jumping down someones throat, I've seen quite a few posts, not specificly by you, but others asking for 3.5 support. Its not here yet, don't ask, because we don't know either, but as soon as we do know, we will tell you, we promise :D

Not at all by me ;)

Providing hacks for Beta Software somehow defeats the purpose of a Beta. Beta software is released so bugs can be sorted before going into RC state. If you would modify Beta's with hacks, there will be no good reference for the coders of vB3.5 Beta anymore.

There is something to say to allow this in this special case with vB3.5 however. Since one of the improvements in vB3.5 is theway Hacks can be incorperated into it, it would be nice if that part of the software could be tested during Beta stage also.

I personally agree to not have hacks until the RC comes out. I imaging what vB.org would do is create a new category under which 3.5 hacks would be posted; much like the current v2 hacks vs v3 hacks categories are now.

Then again, I also agree that we need to wait for the code. As anxious as all of us are (me included), let us not try to break it before it comes out.

My opinions.