vB3 Update Announcement

[Scott MacVicar]

I was just wonder if anyone has any feedback regarding the update announcement that was posted last night?

http://www.vbulletin.com/forum/showt...threadid=67782

[filburt1]

Nothing surprising but I guarantee half the replies will be "when's it going to be out, I've been waiting forever!" and the other half will be countering the previous half saying "shut the hell up and let them work, you guys do great work!"

You know I'm right

[Semperfidelis]

LOL
You hit that one right on the head there filburt
What else could possibly be said ?

[Brady]

I'm excited, keep up the excellent work.

Did I fit into one of those two categories? haha.

[Scott MacVicar]

any flaming posts will be deleted straight away.

I'm just wanting to know if you found it useful. Basically updates will be posted so you know where we are in the development stage to prevent questions asking for a release date etc.

[Andrew-ningc]

Well only because you asked scott.

Will vb 3 public beta release be available in German and English when it does achieve the public beta status? (i am english, just wondering if this has anything to do with the time it is taking to do the release).

[edit] Scott i found the post very useful, updates like this stop the questions about when it will be released, its not that we are asking for a release date, we are asking for a status update. Keep putting them out regularly, and i bet you will find the questions of when it is going to be released will drop.

[nuno]

I was just wonder if anyone has any feedback regarding the update announcement that was posted last night?

http://www.vbulletin.com/forum/showt...threadid=67782

As a matter of fact, I do, the date is wrong, it was started at February 26, not March 6.

Still To Do / Be Completed:
* The vB3 style
* Conversion of all text to use the language system
* Statistics
* Install Script
* Import Scripts
* vB3 Documentation

The vB3 style - It has been said numerous times that vB3 will not be shipped with the new style until it hits Gold.

Conversion Packages - There's a post by Steve that explains this, they are independent.

Statistics - NOoooooo, I don't need that.

Install Script - But the Upgrade script is finished right?

Import Scripts - Same thing as Conversion Packages.

vB3 documentation - Not a major issue IMO.

So, it seems vBulletin 3 is ready, release it at will.

[Steve Machol]

As a matter of fact, I do, the date is wrong, it was started at February 26, not March 6.

Corrected. Thanks!

[Dean C]

Well its nice to see you keeping us informed on the progress. I thank you for that

- miSt

[nuno]

Steve's post was like a breath of fresh air, I thank the Jelsoft Team for doing something like this.
The only one thing that keeps bugging me is this:

In addition, the beta testers are operationg under strict conditions of use, one of which is that they are not allowed to modify any of the PHP files in any way (ie: no hacking).

Is there any strong reason for this, the "no hacking allowed" part?

[vBR]

Steve's post was like a breath of fresh air, I thank the Jelsoft Team for doing something like this.
The only one thing that keeps bugging me is this:

Is there any strong reason for this, the "no hacking allowed" part?

I would assume so the hacks don't fix or create bugs.
The whole point of the private beta is to be a contained shake down of a known quantity in varied conditions.

[Wayne Luke]

Conversion Packages - There's a post by Steve that explains this, they are independent.

Import Scripts - Same thing as Conversion Packages.

Language Conversion has nothing to do with the Import scripts. It has to deal with getting all language out of the templates and putting them into phrases for easy translation (basically loading an XML file). Currently this is not done and was not done during development, mainly because the templates are converted vB2.X templates.

[Scott MacVicar]

no hacking as we want to find out about the bugs in vBulletin not the bugs in hacks.

[Wayne Luke]

Steve's post was like a breath of fresh air, I thank the Jelsoft Team for doing something like this.
The only one thing that keeps bugging me is this:

Is there any strong reason for this, the "no hacking allowed" part?

Yes.... We want to test our developer's code, not theirs.

[nuno]

Yes.... We want to test our developer's code, not theirs.

LOL, Okay, thanks guys.