Crazy product development cycle for 3.7
What on earth got into the minds of the WordPress developers with the product development cycle for version 3.7? Do these guys realise how long it takes webmasters with multiple WP sites to save the databases, save all the files, update the version and re-save everything (which with no rollback option is the best way of ensuring smooth problem-solving if the update breaks anything). I’ll let you know – it takes a long time.
So, WordPress 3.7 Beta 1 was released on 28 September, Beta 2 on 10 October, RC on 18 October, RC2 on 23 October and, a whole day later, on 24 October, 3.7 “Basie” emerged.
Then on 29 October 3.7.1 was released, with mods such as “Images with captions no longer appear broken in the visual editor”. Shouldn’t something as fundamental as this have been noticed in testing? So, just 5 days after a release, I and others have to go through the whole process again.
When 3.7 Beta 1 was released, the comment on the news page was “For WordPress 3.7 we decided to shorten the development cycle”. Well thanks guys, I hope you enjoyed your short development cycle. It has been a complete pain in the neck for some of us.
- The topic ‘Crazy product development cycle for 3.7’ is closed to new replies.