Please slow down new versions…….

LOL….

What? Really? 3 months is an eternity in software development.

M$ took years working on VISTA and look what a piece of $hit that is.

I like the short rev cycle of WP!!!

Not so easy to deal with when you’ve got 10 sites to update, test the themes, plugins, remember if you’ve made any customisations or modifications to core files…

2 years is probably pushing it 9-12 months would work fine, or, as has been requested, a simpler method of upgrading (e.g. auto-update, or at least just a package with changed files).

I’ve been using this script on a server with 3 installs. Priceless and painless.

https://www.thecodecave.com/EasyWPUpdate

3 month for a new major version is just too short.
Look at Micro$oft ??

I would be happy with 2 yearly version well tested!
-m

sorry for my english, i was suggesting a 6 month minimum time between versions. if the devs go faster people will remain behind, updates of a full blog are complex…not to mention themes incompatibilities….

No one is forcing you to upgrade to the latest version. Would you rather use software with security holes than one that is updated frequently?

Subversion

I also would be happy with 2 yearly version well tested!

“No one is forcing you to upgrade to the latest version. Would you rather use software with security holes than one that is updated frequently?”

Actually, it would be nice if “security patches” (only containing the altered files) were released when holes were fixed. As it stands, the minor update process is pretty clunky—unless, as jonlandrum mentioned, you’re using SVN. But not everyone has sufficient server access to run SVN. Sure, they could switch to more expensive hosting plans which would allow them to take advantage of subversion’s benefits, but if they had such money available, why would they be so gung-ho about using free software? ??

Also, SVN doesn’t address the plugin incompatibility issues. If anything, it would only serve to exacerbate that issue.

There’s no need to install any script.

Use the subversion thing. Then set up a cron job to “svn up”. That’s it. No more worrying.

I still use wp2.2, and did not upgrade to version 2.3.

wpnety,

I had the same approach about my site until recently. I figured that I liked the way my site worked, and I didn’t feel like updating my theme (which I wrote, so I couldn’t just wait for the developer to come out with a new one). so I kept the same version of WP for a little over a year and a half.

then one day, all of a sudden, I received thousands of bounced E-mails that had been sent from my E-mail server that I never wrote. My site had been hacked and used to send out tens of thousands of phishing E-mails, and my host shut off my account within the hour. That took a lot of time and energy to recover from, not to mention, it put me on thin ice with my host. It could have been a lot worse. If they had been more malicious, they could have used their security breach as a foothold to hack into my hosts shared server, and destroy hundreds of accounts. That would have gotten me kicked out for sure.

my puppys site also kept the same version of WP for a little over a year and a half. I have to upgrade to new versions already.

thats not a wordpress site, why are you spamming these forums with a non wordpress site, wpnety?

Sorry ， just now enter a wrong site.
here: https://hevin.com.cn, this is latest version site.