December 25, 2012 at 10:15 am #7370
New releases and major upgrades (1.0 -> 2.0) are announced in the StudioPress blog or the StudioPress Twitter feed. But the minor releases (1.0 ->1.1 or 1.0 -> 1.0.1) are never announced. And StudioPress doesn't push theme upgrades through the WordPress admin panel. So the only way to keep up-to-date is to visit My StudioPress to check the current version of your theme, then go back to your site to see what version you're running. Additionally, there is no changelog.
I wish there were a centralized place or feed where one could monitor all the releases, major AND minor, along with the changes.December 26, 2012 at 2:39 pm #7553
Thank you for the recommendation. Generally the "minor" updates are not announced because there usually isn't a need to upgrade. When the update is fixing an important bug we do try to send out notifications. I'll check to see if there might be a way to be more active in sending update availability information out. Generally it isn't intended that child themes be updated however.December 26, 2012 at 8:18 pm #7612
I like to have the latest and greatest. If it's important enough for StudioPress to release it, then I want it.
With stealth, unannounced releases, it makes it hard for users like me.December 26, 2012 at 10:34 pm #7648
We are making some changes to the development system so it might be possible to have an update system like this. I can't promise anything, but I can see if it might be possible to create a feed of sorts for users looking to the latest. The difficulty is separating theme updates from development updates that are not live. We do plenty of behind the scene updates, especially with Genesis, before pushing the release product out there.January 8, 2013 at 4:52 pm #10484
EXAMPLE: Genesis framework 1.9.0 was released yesterday, 1/7/2013. The next day, it was updated to 1.9.1. But the update wasn't announced anywhere as far as I can tell. I just checked the StudioPress Twitter account... no announcement. I checked the StudioPress blog... nothing. If the core framework is updated, doesn't that warrant an announcement?January 8, 2013 at 4:59 pm #10485
An email went out to the mailing list and there was a blog post on the 1.9.0 update
The 1.9.1 update addresses an issue and was pushed as soon as we found the problem. Since the 1.9.0 updates are literally still being read for the very first time by the majority of users we didn't do a second email campaign or blog update.January 9, 2013 at 9:25 am #10685
You must be logged in to reply to this topic.