I’m glad to see this poll and I hope it will get enough responses to provide a clearer picture of the current Magento update landscape. My personal feelings have already be posted elsewhere in these forums. In short, I think this is a great update - when it works. First-time installers are in a much better position than those, like myself, who are updating. I manage several live Magento stores and I won’t let this update anywhere near those servers yet. But I’m looking forward to the day when I can.
On the plus side, I can say without hesitation that this update has some serious back-end performance enhancements. For large sites there will be a definite noticeable improvement. For smaller sites or those just starting out, you may be able to get away with a less muscular server environment thanks to these optimizations.
Just a short snapshot before closing the poll and proposing conclusions.
Out of the 40 responses at this instant:
- 11 (27,5%) managed to get the update to work OK
- 17 (42,5%) were still fighting to make it work AT THE TIME WHEN THEY RESPONDED (they might have change situation since, but no way to know this thru the poll)
- 12 (30%) did not upgrade or reverted back (7,%)
Ignoring if additional votes follow the same pattern, I would propose 2 TEMPORARY conclusions:
- 1.2.0 and its sibling 22.214.171.124 (for the record, just issued some hours after) were not at the quality and safety levels that can be expected from a “STABLE-labelled” upgrade
- Magento dev team should question their quality assurance process and leave such version longer in a BETA state, so that the upgrade is not silently forced to users and more debugging is made
Unfortunately, this poll will be mostly seen by people browsing a forum dedicated to upgrade issues. Hard to get feedback here from people who had no problem ! I would have like to know which config they have, how they did, if it was their first upgrade or if they update Magento since the first beta… Can be sure that something in the 1.1.0, updated to 1.1.4 then to 1.1.8, without upgrading to 1.1.5/6/7, is not now an issue in the 126.96.36.199 ? An issue that people upgrading from 1.1.8 won’t have as they where before on a fresh install of the 1.1.8… Do you see what I mean ? :D
As far as I’m concerned, I’ve done all upgrades since 1.1.0, and I had to do a full “clean” install of 188.8.131.52 OVER the 1.1.8 database to get the 184.108.40.206 usable. But I still have some bugs with catagories, client information update…
I get error both with Magento 1.2 and 220.127.116.11.
I suggest a 3-4 months of development without new feature but only bug fix with regular weekly release.
Once Magento will be stable continue adding new feature.
@daynos: I agree with you, no poll can pretend to be a perfect mirror of reality. And in the case of this poll, certainly people with problems will be more prone, while they serach for solutions, to find this poll. While problemless people will probably not see the poll, even if I have been posting on “success” threads.
What it shows though is that qualifying 1.2.0 and 18.104.22.168 as “stable” was probably not appropriate.
Maybe Varien should consider an interim state between beta and stable, such as RC (release candidate) with the meaning ‘we feel pretty confident that this is working on all the machines we have tested, but we do not pretend that it is stable until lots of people have installed without problem’.
Qualifying the relase as “stable” had the unfortunate side-effect that in lots of cases users were not offered the possiblity to opt-out. THAT was, in opinion, the mistake.
The most upsating point is that I did all update since the launch of 1.1.0 without any problem, and the last update before launching my best friend shop was that one that brings bugs :/ And no possiblity to roll back as she was filling products all week long…
We can consider now that the situation is pretty well stabilized and that there will be no significant percentage change.
-- Number of tallied responses: 76 (for >500 views of the post)
-- Successful change, with minor adjustments if needed: 19 (25.0% of total tallied responses)
-- Change made but not yet fully operational, waiting for some divine intervention from the community/forums of from the dev team: 29 (38.2%)
- Still in previous version: 28 (37.8%), of which 7 (9% total responses) switched back.
HOW TO INTERPRET THESE FIGURES?- there are some biases you need to be aware to interpret these figures:
—happy upgraders are underrepresented, since they are less inclined to search thru the forums for a bug they did not meet
—the poll does not allow answerers to change their response later. This means that since they answered, people might be in a different situation (eg, solving all their problems and going “up” or finding problems they had not met yet and thus going “down")
HOWEVER the heavy figures of unsatisfied persons should ring an alarm bell at Varien to improve the quality of the upgrade process in several areas:
-- the upgrade process itself seems to ignore problems with access rights, ie assuming a level that is not part of real life. As a result,
—some parts of upgrades canNOT be achieved, and the warnings from Magento-Connect are not relayed as visibly as they should; this seems to have created a major problem with 1.2.0.x where parts of the upgrade could not be transferred
—some upgrades, successful as far as file transfers are concerned, are rendered UNsuccessful because they leave rights too lax (dirs at 777, files at 666 where it should be 755 and 644) and this is blocked by the hosting providers
- the versioning system should be improved:
—longer observation period between a time when a version is first released as “beta” and then switched to “stable”, maybe as I said earlier with an addition ”release candidate” step
—NO SILENT UPGRADE without asking ..
this upgrade or new function you install will require that you upgrade Magento from your current version 1.1.X to 1.2.0.x. Which option do you select:
—cancel this operation
—get a previous version (x.x) of the funtion you want to install: this is compatible with your current Magento version 1.1.X
—I want first to achieve a successful upgrade to 1.2.0.x, the testing, before installing this function
—I want to proceed: install the function and make all necessary upgrades (I understand it is not wise to do that on a production system)
Your suggestions and conclusions of these proposal are welcome, we need to make constructive propoosals…
My experience shows that 1.16 is the stable version and anything beyond has had some major issues. Don’t get me wrong, the Magento team is producing an awesome product at an unbelievable deal. In a year or two we will look back and laugh but until then we just have to use what works.
Anyone that has a serious issue with the magento team needs to seriously thing about what they are getting for FREE! Yeah it has issues but it’s still in its infancy. Just don’t install the upgrades on your production server until you are positive that it works with your system that’s all.