[adamdavidconn]

thats means they are probably trying it again.

well, hopefully this time it will work.

[Fynnon]

They had to make this update because you cant sell something people cant see in action !

[johnrizz]

Yeah, well think again!

[adamdavidconn]

maintenance redirect back up

i think its try #2

[Trevor Hannant]

Originally Posted by adamdavidconn

maintenance redirect back up

i think its try #2

2!?

[Bounce]

or try 22

[Ingenious]

Agree with the comment above "dammed if they do, dammed if they don't". Let's give them some slack, I'm looking forward to seeing this, and would rather see an early and possibly unstable release than wait months!

[Link14716]

.

Originally Posted by Ray Morgan (here)

Greetings all,

Well, we've had our share of excitement this morning, and since this thread was going on, I hope you don't mind my popping in to explain what's going on over at vb.com.

We decided to take some extra time before bringing the forums back up this morning after the upgrade to 4.0. Briefly, here's what happened.

First, the good news: The installation of 4.0 itself actually went as planned. The upgrade to 4.0 Publishing Suite from the 3.8.4 base product was seamless, and that agrees with the success the alpha/beta team has seen up to this point.

The issues we encountered were related to the fact that the instance of vB running on vBulletin.com has integration points with various business systems: administration, release management, ticket support, the product information site, and more. Cooler heads make better problem solvers, so we chose to investigate and solve the problems with the site offline rather than live to the world.

The issues we ran into are unique to our environment, and they are not things that would factor into a normal customer installation.

Our forums are actually up, running and stable now, but are only accessible to our internal staff. Given that this is such an important upgrade, we're taking our time and being careful, and we're planning on opening our forums back up tomorrow morning.

.

[steven s]

Thanks, but I think posting on vb.org would have been more appropriate [for Ray].

[Dave-ahfb]

I hate to insert common sense into an IB related concern, but I guess I am just bored. Do you think this means they may now extend the deadline past the 30th? nah, forget I asked.

I am going back to stare at the vb maintenance page, the one that shows the guy with his head stuck in the sand.

[steven s]

Originally Posted by Dave-ahfb

I hate to insert common sense into an IB related concern, but I guess I am just bored. Do you think this means they may now extend the deadline past the 30th? nah, forget I asked.

I am going back to stare at the vb maintenance page, the one that shows the guy with his head stuck in the sand.

I recall that beta sites would be public.

[Adrian Schneider]

Originally Posted by jmurrayhead

You're basing your willingness to upgrade to 4.0 off of the first Beta??

Yes and no...

The sites I work with also integrate into other pieces of software or custom code. This actually a huge reason to hold off on upgrading, because these integration points are what will cause the real problems. I don't mind updating a style or a few plugins, but if all our custom coding fails because the code it's anchored to has changed or is gone, then we're up the creek if we jump to the latest version too early.

However, thorough testing and a good staging site can catch these problems. Sometimes a simple backup / test on the forums is not enough - you have to test the entire site and its suite of applications. This is another reason I'm a strong advocate of unit testing -- these kind of things can usually be caught at the flip of a switch (or pound of a button).

Also, there's no guarantee that these problems are truly unique to their set up. If the problem caught them, it can catch others with custom code too - it's impossible to say.

Knowing that the site is still down 8? hours later with the team that they have is VERY alarming. Hopefully this doesn't paint the picture for those upgrading a lot of custom code.


This is obviously an extreme view coming from a developer. This should not be an issue for the vast majority of other license holders.

[jmurrayhead]

Originally Posted by SirAdrian

Yes and no...

The sites I work with also integrate into other pieces of software or custom code. This actually a huge reason to hold off on upgrading, because these integration points are what will cause the real problems. I don't mind updating a style or a few plugins, but if all our custom coding fails because the code it's anchored to has changed or is gone, then we're up the creek if we jump to the latest version too early.

However, thorough testing and a good staging site can catch these problems. Sometimes a simple backup / test on the forums is not enough - you have to test the entire site and its suite of applications. This is another reason I'm a strong advocate of unit testing -- these kind of things can usually be caught at the flip of a switch (or pound of a button).

Also, there's no guarantee that these problems are truly unique to their set up. If the problem caught them, it can catch others with custom code too - it's impossible to say.

Knowing that the site is still down 8? hours later with the team that they have is VERY alarming. Hopefully this doesn't paint the picture for those upgrading a lot of custom code.


This is obviously an extreme view coming from a developer. This should not be an issue for the vast majority of other license holders.

Perhaps I'm being misunderstood or I misunderstood the posters I replied to. I took their comments as they wouldn't upgrade their sites to 4.0 when the software was considered stable (this coming from the fact that nobody but the beta testers have access to the beta version). That's what it looked like to me. Of course I wouldn't upgrade my live site with a beta...but since IB isn't offering the beta to customers right now, that's not even an option anyway.

The issues we encountered were related to the fact that the instance of vB running on vBulletin.com has integration points with various business systems: administration, release management, ticket support, the product information site, and more. Cooler heads make better problem solvers, so we chose to investigate and solve the problems with the site offline rather than live to the world.

So Ray and the new batch of developers didn't know this in advance? Woooooooo

[edytwinky]

I anxiously await the morning!