Beta Release VIII

colinpreedy · 2010-09-30T23:39:20.000Z

Hi Nic,

in your release notes you write that we shouldn’t upgrade from other beta releases to release VIII.

In other words if I want to test release VIII, I need to backup my current version ( 5.0.56294 ), uninstall it, install release VIII and copy the backed up folders Data and DB into the Spiceworks directory.

Did I understand that correctly?

Cheers,

Colin

bytesnake · 2010-09-30T23:46:40.000Z

Nein.

Er sagt, man solle von 4.7 upgraden. Also 4.7 installieren, Daten aus dem produktiven Betrieb zur Testmaschine kopieren, dann mit Beta 8 upgraden. Nur auf diese Weise sieht man, ob sich Fehler eingeschlichen haben, die bei einem Upgrade von einer früheren Beta nicht auftreten.

jim · 2010-10-01T05:03:37.000Z

bytesnake wrote:

Nein.

Er sagt, man solle von 4.7 upgraden. Also 4.7 installieren, Daten aus dem produktiven Betrieb zur Testmaschine kopieren, dann mit Beta 8 upgraden. Nur auf diese Weise sieht man, ob sich Fehler eingeschlichen haben, die bei einem Upgrade von einer früheren Beta nicht auftreten.

My German is a little rusty, but that’s it.

colinpreedy · 2010-10-01T05:16:08.000Z

I understand what Nic wrote but that doesn’t answer the question I stated here.

I would just like know if upgrading the Beta Version I have installed on a testmachine will work the way I describe above.

bytesnake · 2010-10-01T05:23:34.000Z

If you dont have a 4.7 environment, or dont want to test if data migration from 4.7 to 5.0 works, still run the installer at your test maschine. No needings to uninstall previos beta.

jim · 2010-10-01T05:32:21.000Z

Colin9172 wrote:

I understand what Nic wrote but that doesn’t answer the question I stated here.

I would just like know if upgrading the Beta Version I have installed on a testmachine will work the way I describe above.

I just install over the other beta as I am not testing the migration of data from 4.7 to 5.0. So yes, you can just upgrade the beat release on your test box.

colinpreedy · 2010-10-01T05:36:45.000Z

Thanks Jim,

that’s what I wanted to know. Have a good weekend.

jim · 2010-10-01T06:21:21.000Z

No problem Colin! Glad I could assist. Have a great weekend yourself.

Connie-K-Spiceworks · 2010-10-01T09:26:29.000Z

The upgrading of Spiceworks from beta to beta is not recommended for many reasons. One of them being bugs in previous betas can affect the current state of your data. We had bugs in our early betas in how some data was stored. International users who use special characters would for sure be affected.

It’s not just the testing of the migration that we ask you to go back to 4.7 data. In upgrading from one beta to another you are moving forward data that may have issues that we have corrected in the current beta. The migration will not catch these issues and you could later run into problems where the application doesn’t expect the data in this state.

From beta to beta we have made changes in our database structures and so we encourage you to start from scratch.

I hope this explains some of this issues and why we have asked you not to do this. In general it’s a beta and not considered ready for production due to working out all these issues.

This is not a new request from Spiceworks. We have asked this in every beta but in the past you may not have been affected when ignoring our warning.

Connie

jim · 2010-10-01T09:35:06.000Z

Connie (Spiceworks) wrote:

The upgrading of Spiceworks from beta to beta is not recommended for many reasons. One of them being bugs in previous betas can affect the current state of your data. We had bugs in our early betas in how some data was stored. International users who use special characters would for sure be affected.

It’s not just the testing of the migration that we ask you to go back to 4.7 data. In upgrading from one beta to another you are moving forward data that may have issues that we have corrected in the current beta. The migration will not catch these issues and you could later run into problems where the application doesn’t expect the data in this state.

From beta to beta we have made changes in our database structures and so we encourage you to start from scratch.

I hope this explains some of this issues and why we have asked you not to do this. In general it’s a beta and not considered ready for production due to working out all these issues.

This is not a new request from Spiceworks. We have asked this in every beta but in the past you may not have been affected when ignoring our warning.

Connie

Connie, thank you for the explanation. And I wouldn’t say I ignored your warning, I took heed and made a discussion to move forward based on what I was seeing and the fact that most software will not have up to eight beta releases. Not bashing anything on that statement as I have said many times before and stand by it that I would rather have 12 betas to go through than to see SW start to act like MS and release garbage to the community.

So on that note, I moved to production with the b6 release as I honestly thought we were closer o a release than we were. No big deal. If I have to lose some data, then so be it. Lesson learned.

justinsmall8324 · 2010-10-01T10:00:46.000Z

I’ve been using the 5 beta in production since beta1 and i have updated the beta

jim · 2010-10-01T10:21:35.000Z

Didn’t find this to be very nice:

Nic (Spiceworks) marked a best answer. (39 minutes ago)

Nic (Spiceworks) unmarked a best answer. (39 minutes ago)

@Colin9172 marked a best answer. (5 hours ago)

nic-spiceworks · 2010-10-01T13:49:19.000Z

Jim Kubicek wrote:

Didn’t find this to be very nice:

Nic (Spiceworks) marked a best answer. (39 minutes ago)

Nic (Spiceworks) unmarked a best answer. (39 minutes ago)

@Colin9172 marked a best answer. (5 hours ago)

I changed the best answer so that folks would see Connie’s reasoning why not to upgrade from one Beta build to another.

stephenmurphy9597 · 2010-10-01T15:27:31.000Z

Successfully installed 5 Beta 8 with a scan and a network config pull. What data should I be looking for to validate this feature for you?

-Murph