vBulletin 2.0 RELEASE CANDIDATE 2 Released

[John]

Discuss away!

PLEASE remember to post questions/suggestions/bugs in the correct forum. Also, if you are posting a bug ALWAYS do a search before posting!

John

[eva2000]

great news ..... goes off to upgrade hehe

[h4p3]

One question, is the ubb6 import script included in the final version?

[Kier]

We are working on the UBB6 import script. If it's not included in the final release, it will be available in the members' area soon afterwards.

[Craig A]

Bloody hell! I've only just (10 minutes) finished updating to RC1!

[Kier]

The RC2 upgrade is very painless...

[h4p3]

Kier ... good to know. I can't wait for the Import Script :)

[WebAddict]

Bloody hell! I've only just (10 minutes) finished updating to RC1!
I Just upgraded to RC1 this morning... I need to get on the ball. I am upgrading now to RC2... Oh well. This is why I don't have any hacks installed yet.

[klisis]

It was smooth upgrade. I like the new location of smile box.

[eva2000]

beside the parse error i had in the original RC2 upgrade7.php file, everything went well :)

[nuno]

Originally posted by Kier
The RC2 upgrade is very painless...

oh noooooo :(

[Kier]

Originally posted by nuno
oh noooooo :( painless

[nuno]

Originally posted by Kier
painless

you are right Kier, stupid me!!
nevermind
terrible headache today

[Hooper]

Kier,

I think the way you upgrade is just wonderful. No problems.

Have some rehacking to do though! NewsFader is a must! GimmeTech:D

Now should I revert to original templates again and rehack everything or is this necessary as it was in Release Candidate 1?


Thank You,
GimmeTech

[bokhalifa]

good warkin:)



wit templates_changed
in templates_new

for
RC2
:)
good news
Thank You

[Fred]

Looking good my friends. Cant wait till the final release is out.

[Nicholas Brown]

smooooth.
You guys a re too dam fast ;)
BTW. Smilies look better on the right :p

[Steve Machol]

Originally posted by GimmeTech
Now should I revert to original templates again and rehack everything or is this necessary as it was in Release Candidate 1?

Hopefully Kier will correct me if I'm wrong, but I think you only need to revert the templates that were changed. A list of these templates is on the Announcement Forum message for this release.

[Hooper]

Hi Steve,

Yes, I realize what you are saying, I'm just wondering if it is necessary to revert back to original for this release. If not, all I'll have to do is add my hacks back in. I believe the reason we had to do that in the RC1 from Beta 5 was that there were template fixes of importance (netscrape) in this update amoungst other things. I read the updates page and see what's updated. I also didn't do the revert to original to my templates at first with RC1 and was amazed when I did. I just want to hear it from them though. And as you well know Steve, I have numerous templates to change. I'm just dying to hear that it isn't important.

Thanks Steve,
GimmeTech

[Kier]

This release has far fewer templates changed, as I did the majority of work for RC1. The templates that have changed are listed in John's announcement, and most of those are very minor changes, which should be easy to integrate into any customized templates you have.

[Hooper]

Ahhh,

That wasn't so bad. Thanks Kier.

GimmeTech

[Jake Bunce]

eva, parse error in the upgrade7 script?

Anybody have issues with this upgrade so far. I'm gonna do mine tonight and want to know if there are any issues I will need to deal with.

[Kier]

If you downloaded the zip five minutes after the announcement was made, you will not have a parse error.

[Jake Bunce]

Just upgraded, no problems encountered.

eeeeeexcellent...

[tamarian]

I upgraded to RC1 after the announcement, and while the forum is closed, upgraded to RC2, no problems.

Kier, now my CP looks better than my forum?! :)

[KeithMcL]

Upgrade complete, pretty smooth.

Well done guys!

[urbanways]

good looking people cant wait until the final version is droped

[firewire]

Board upgraded like a charme... now give us final stuff so vB 2.0 can go into production! :)

[CoolaShacka]

I have a feeling when I look on the calendar, http://www.vbulletin.com/forum/calendar.php.

On Mai 1. I will update to 2.0 final! ;)

[tamarian]

Originally posted by CoolaShacka
I have a feeling when I look on the calendar, http://www.vbulletin.com/forum/calendar.php.

On Mai 1. I will update to 2.0 final! ;)

Might even be sooner, only 2 bugs or so after release. :)

[Goodieman]

hey guys, I think you've done a great job.

but i'm affraid the company i work for won't allow me to update to a non-final version.

i know you're very reluctant, but can you give any update on how things are progressing? I think you're so near the end, you could give us a couple of dates (like: between.... and .... is the target date)

damn...i can't stop whining, can i ;)

can't wait to show my visitors the new forum

[Freddie Bingham]

If you are lucky than this week.

[Hooper]

Ah finally out of the bag. :eek:

[Fred]

Today is May 2, 2001 - No release.. DAMN

[handinhand]

Originally posted by Fred
Today is May 2, 2001 - No release.. DAMN

Too.

[DeMoN]

may 3rd no release :(

[handinhand]

:(:(.............................................. .:( :(

Waitting......?

[Freddie Bingham]

Try again next week. Sorry.

[h4p3]

Are there still so many bugs? I didn't find anything :)

[RobAC]

Remember everyone.......haste makes waste.....I'd rather see the developers take their time and do a thorough job than to rush through it and release a flaw-filled, unreliable heap of trash. :)

Now with that said.....HURRY UP!!!!!!!!!!!!!!! :D :D :D

[JackG]

I think the Developers have done a GREAT job so far!
Maybe they should just take it easy for a week or so.. smoke some funny cigarettes.. then look into finalizing the forum.



:eek:

[mmania]

Hey guys!
There is the problem with referrals.
That function doesn't work in Candidate 2.
How to fix it?
Or maybe I use unproperly URL?
Please help, i'm in hurry.

[Fred]

Why would it be release next week? There are no more bugs. Just UBB6 import script testers.. grr.

[Mike Sullivan]

Originally posted by Fred
Why would it be release next week? There are no more bugs. Just UBB6 import script testers.. grr. Just because there aren't any bugs (which there are; there always will be), doesn't mean we don't have stuff to do. The UBB6 import in no way whatsoever effects the release date.

[mmania]

Hey guys!
How about the referrals bug?

[Mike Sullivan]

Not a bug -- you're either using it incorrectly or don't have it enabled. I suggest you use the search as it's been covered extensively.

[mmania]

Ok.
How to use it properly?

[robertusss]

I don't like the way you HTML-code the pages , so I spent A LOT work on reworking the templates for us (we run beta3) und now I learned, that the templates all changed again (grrrr). Can somebody please give me an overview on what template changes we'll see from RC2 to stable?

[Kaya]

If you spent "A LOT" of work, you have only yourself to blame.

Beta software is just that: beta software - no guarantees and no promises attached.

What would be the alternatives?
1. VBulletin programmers always stick to old, once-established, obsolete templates and never improve anything to avoid "change"
2. VBulletin keep all their programming in secret until they release the final version with no user feedback and longer waiting for the impatient.
3. VBulletin spend time on "giving some guy an overview on what template changes we'll see from RC2 to stable" instead of spending time on creating a final version.

Frankly, I don't like any of those three alternatives, just because some people can't wait a couple of weeks before they start hacking away on an un-released software.

To the programmers: I think you're doing a good, fast job!
I mean compare this to the release schedules of the big software companies...

[Hooper]

I agree with the above. I have RC2 isntalled with about 10-12 template changes and 4 hacks. You can either wait until the final, or redo each time you upgrade. To be perfectly honest, with all of my changes, it still only takes about an hour to redo everything upon upgrade. No big deal. I like the way vBull goes about the upgrades. You could always get UBB and update once a week. Every time you turn around there is another release. Since 6.0 came out there have been 7-8 updates. UBB Gold also gave Beta a new name.

Think not. I'm happy with vB.

[MrArtic]

While i wait for the final version i spend time doing other things that doesnt affect vbulletin, i made an integrated chatsystem and a postcardsystem :)



Originally posted by robertusss
now I learned, that the templates all changed again (grrrr). Can somebody please give me an overview on what template changes we'll see from RC2 to stable?

[tubedogg]

Originally posted by Hooper
UBB Gold also gave Beta a new name.

ROFLMAO!!!!

oh my god that was so perfect!

[Hooper]

Originally posted by tubedogg


ROFLMAO!!!!

oh my god that was so perfect!


True too. After receiving acknowledgement from UBB of finding totally screwed templates in the Gold version, It took another week to get the darn templates fixed. Then I found more of them. Once fixed I went to report another issue and found that it was reported in January way before the Gold version was released.

"BetaPop Corporation"

[Steve Machol]

Originally posted by Hooper
"BetaPop Corporation"

Believe it or not someone has already registered the domain BETAPOP.COM!

By the way UBB6 is on it's eight bug-fix release since it went Gold just a few weeks ago! :eek:

[Hooper]

Well.... Not exactly. That is 8 new updates versions each with a wide variety of bug fixes. To many bugs for anything named more than Beta. If this is what you are saying......I say exactly.

[Cosmic Cubes]

Can any body tell me when upgrading for a version ( I have not upgraded from the beta version yet) that if i upload all the files as John says to on this forum.. will i loose all my registered members?? I dont think so but i would just like to be sure before i do it.. Im new to this as i used to have UBB but brought this instead.

Thanks

Cosmic

[tubedogg]

No you don't lose anything.

You didn't really with UBB, did you, though?

[handinhand]

:):).............................................. .:):)

Waitting......?

This Week......

[robertusss]

well, you missed my point. All I wanted to know if the vB-Team has finished with their work on the templates or not. maybe they are right now only finishing the manuals and the install-script and the rest is ready to be released.

[claypots]

just wanted to say that was a terrific upgrade experience! I love the rush I get when installing web-based sftware! :) gj.

BTW what is pm tracking?

[robertusss]

just to make 100% clear: I read in an post from one of the developers, that the code of 2.0 is "frozen" and new features will have to wait for 2.1.

so my question was (and is): are the templates also already "frozen"?

thanks

[tubedogg]

Not necessarily. If they discover a bug that would prevent something from working in the templates, they'll fix it. The code is only frozen so far as adding new features or options. The only code changes they are making now is bug-fixes.

[tubedogg]

Originally posted by claypots
BTW what is pm tracking?

PM tracking is an option that allows you to learn whether or not someone has read your PM. The recipient of your PM can refuse, or deny, sending this "read receipt" if they wish when they receive your PM. If you click the dropdown in the upper-left of the main PM screen, where it says "Inbox", you'll see an option for PM tracking.

[Kaya]

robertusss,

you are probably referring to this from the FAQ:


Can You add this great new feature to the software?
The feature set for vBulletin 2.0 is frozen however we will review your suggestion for future releases.

If the code was frozen, they would not be able to fix bugs. You can only fix bugs by changing code. Same with the templates: They can't tell you if there are no more changes until they cleared all the bugs.
And even if they could tell you, why should they commit themselves?

We are still in beta stage, with features frozen - If they find a better way to work with templates under the same feature set and that means changing the templates - I think they should go ahead with it during the beta stage.
If they made committments now they would restrict their work or make people like you angry when they have to break their committments. (angry like you were in your original message, by the way: "Were you really asking for a simple yes/no answer back then?")

I think the problem here is that you don't understand the principles of "beta" and "beta testing". A beta stage is without guarantees and promises - if beta software ends up erasing your hard drive - tough luck, but you can't blame the developers.
If betas came with any guarantees, it would restrict the work of programmers/developers unnecessarily. A beta should be reasonably tested of course (unlike alpha), but it certainly does not involve any "code freeze" guarantees.
A release candidate is a possible candidate for release but still beta software. A feature freeze concerns the set of features but not how they are presented or implemented. It normally is meant to say: "Hey, stop bombarding us with new feature requests until we finish this!" and not "Honestly, we promise, no more new features!".

To sum up: I think it's dangerous to get developers to oblige to anything during beta stage - If they come up with a new feature after a feature freeze - well ok, they changed their mind.
During beta: report bugs, report bugs, report bugs, accept the facts of life
After beta, with the final release - complain, complain, complain

[Kier]

Indeed the feature set is frozen. This means that we are no longer accepting feature requests for this version of the software, although all feature requests and suggestions are considered and logged, so that we can go through them properly when we start development of the next version.

We are trying very hard not to make any major changes to the code or the templates at this stage, but sometimes we discover something that will require us to make some alterations to something or other. A situation like that arose yesterday, and is the reason why we will be releasing RC3 instead of the final code. (Don't ask, we'll tell you later).

If we had announced that we were going to release the final code today, and then we didn't for whatever reason, you wouldn't be best pleased would you? For that reason, it is our policy to not announce a release date until the code is actually released. Sorry if that upsets anyone's plans, but that's the way we have to work.

[firewire]

Kier:

Hard to acknoledge for the impatient like myself, but nevertheless, I highly appreciate your efforts to release a bugfree (if ever possible) vbb rather than beta-soft which needs 6 "service packs" aka bugfixes.

So, allright with me :)

[Hooper]

Agreed....;)

[Oasis]

PM Tracking tells you what has happened to the PM you've sent. i.e. if it has been read by the other party. Very cool feature :cool: