tralala
+84masterchief wrote:Users have a right to be concerned, and many of those concerns have directly shaped 1.6 and I've even personally coded some of them, but when you are getting something for free from someone else's efforts, you also have certain responsibilities. I don't like the fact that we don't have a core upgrade path, but we made a decision back in October '10 for that not to block the release (and we'd made numerous calls prior to that for a team to assemble to own that work). People have had 2 months to contribute to that and so far only one person to my knowledge, with very little help and to his credit, has taken up the challenge in any serious capacity. As I said, now that 1.6 is out I'll be able to allocate some time to that and hopefully others who are capable will follow suit.red2678 wrote:Is that how you respond to user concerns? Seems to be the norm....
So I *do* listen to user concerns but I'm less tolerant of people that are not concerned about who actually has to do the work, as long as they get it for nothing. The effort just to get 1.6 to this place was simply enormous and the migrator project is no trivial offering (to be honest, in hindsight I think the migrator side of things should always be a separate project from the main development arm, but that's something to brainstorm about another time). It's a pain in the backside we couldn't get one into core for yesterday's release, and believe me I do feel "how could I have done even more", but them's the brakes. Reasonable people, I think, can accept when you are dealing with a volunteer workforce, you aren't going to get what you want sometimes and they also realise that when they do get what they want, something else has been sacrificed to get it. No point in having a migration path if 1.6 is completely unusable.
This great and shows how easy the upgrade process is. Thanks, Nick!unworthyslave wrote: Hopefully this will help someone out:
http://docs.joomla.org/Tutorial:Migrati ... Joomla_1.6
We still need a lot of community contribution. You can see some ways you can help at the bottom of the wiki.
Google wasn't much of a help neither... 
bzsolt wrote:Hi Guys!
Nice party here.
Let me share my story:
Approx. 2 weeks ago (which was approx. 2 weeks after I migrated from j1 to j1.5)
Joomla 1.5 will continue to be supported for another year and three monthsbzsolt wrote: I spent the last 2 hrs reading this topic and other articles and I feel much lighter (not yet floating, no) but still don't know whether there will be 1.5.23, 24, etc versions.
I completely agree about needing to have upgrades done by the host. I found the exact same thing... most ignore the security notices. Actually, most of my clients don't even know they are using a CMS. They just know there is a website and they can edit a page or two.davetanguay wrote:Yeah that is what I thought years ago when we started getting a lot of Joomla and WordPress sites on our servers.... but that just isn't the case anymore. When new security releases were available for Joomla and WordPress we'd inform customers of the upgrade and told them they were mandatory. 95% of customers never upgraded and we had all sorts Joomla and WordPress sites get hacked due to them still running old versions. The hacked customers were pretty much clueless as to how it happened... most ignored the notices we sent.severdia wrote:As a webhost, you shouldn't be put in the position of auto-upgrading websites. I won't tell you how to run your business, but I think it's something outside the scope of what a normal webhost normally does.
This not only affected their site but the entire server. The entire server wasn't hacked, but the hacked sites usually caused load issues from the hacker or got us listed on some RBLs which affected all customers on the server... so now we do consider CMS upgrades our responsibility if we can do them easily.
If you're a host and don't think it is your responsibility to keeping scripts updated, think again unless you want to deal with hacked sites and server abuse issues later down the road.
If they are just core upgrades, they don't take long at all if you use Installatron on a cPanel server. Except of course "migrations" like 1.0 > 1.5 > 1.6 but those are not security releases anyways. Migrations are left up to the customer.unworthyslave wrote:I just hope they are paying you Brian, because that is a lot of work!
We've only had 2 customers complain (of about 2,600) in regards to keeping their scripts upgraded so we whitelisted them from our "process".unworthyslave wrote:The larger hosts I have worked with leave it up to the customer, yes.
One issue of updating all the accounts via whm is if they had modified any of the core files (which they shouldn't have, but a lot of people still do frequently), all of modification will be lost.
Another issue is that some 3rd party extensions can break with newer version (although rare).
Have you ever encountered any such issues to date? Just curious
© 2005 - 2024 Open Source Matters, Inc. All Rights Reserved.
