#Openoffice for windows 7 filehippo install
#Openoffice for windows 7 filehippo update
#Openoffice for windows 7 filehippo upgrade

Letting people knowingly corrupt their data without doing something, for more than 2 months, is totally unacceptable. However, it is what it is, and that is a major snafu. I say this with full knowledge of what kind of impact that can have on an Open Source project. This is a HUGE and MAJOR data corruption issue, IMHO it can not wait for normal procedures to be followed to correct it.

#Openoffice for windows 7 filehippo upgrade

its not stable and it should not continue to offer to upgrade people while it has this major issue. Only a couple of them have the rights and access to do that install, still.

#Openoffice for windows 7 filehippo install

Every time I open OpenOffice 3.0.1 it tells me to upgrade to the latest stable version and now I have to field calls from 1,000 users on 1,000 machines whose software is telling them there is a newer stable version and wants them to install it. At least they need to put out the Developer version that has supposedly been released for 2 weeks and is NOT on any mirror anywhere that has the fix.

#Openoffice for windows 7 filehippo update

The project needs to pull this release from the stable trees or they need to update the software to fix this bug well before August. The bottom line is that Stable means Stable and Beta or RC means Beta or RC. they should test any updates before deployment. I was able to do this because I use very conservative testing procedures to deploy updated software. I did so without rolling this out to 1000 machines and costing my company millions of dollars (and me my job). However, I had backup copies and I was able to roll back my software and recover my spreadsheets. 3 very important mission critical spreadsheets. The only way to fix this (after you move back to real stable software) is to hand edit and verify each and every cell of your spreadsheet. Sometimes even in the same data row, some columns are sorted and others are not. Some columns are sorting and others are not. when the sort is done, that cell might now $F$8 even though it should be $E$8. So if you were doing a sort and your formula contained a $E$8. It changes the cell references in some columns when it doesn't sort, but not all columns. It not only is broken (understandable, things break), it is corrupting spreadsheets (not acceptable to release as stable, certainly not acceptable to leave released as stable once discovered). I broke 2 other spreadsheets testing to see if it was a problem. It took me 5 seconds to see it was busted on a very simple spreadsheet. There is no way this should have not been seen by someone. I can't think of a spreadsheet that I use for anything that is even slightly complicated that does not sort on a column with a reference to another cell. If this was a new capability that was added, then that would be one thing however, it is the sort function of a spreadsheet program. One thing I expect is that a majorly used feature, when used as designed, does not corrupt data. However, when a project marks the release as Stable, I expect certain things from it.

I also realize that all 'Stable' software has bugs. I also understand the difference between 'Stable' and 'Beta' or 'RC' software. I am a lead developer for the CentOS project, so I understand the Open Source process.