Headsup: changed the “newui-3.1″ Component to now be called “User Interface” since there’s a need to tag tickets as relating to the overall UI and/or graphics only.
Tickets previously tagged with “newui-3.1″ should now be tagged “User Interface”. Example: http://ios.trac.wordpress.org/ticket/1458
Translated everything remaining in 3.2 to Swedish. Should make it into the next update.
We really should provide some more comments for every new string that we add though, it’s painful trying to figure out how and where and why a string is being used. There were also a few instances of strings that are redundant.. Very similar to older strings or with just capitalization differing. One instance of the exact same string being it’s own entry and then as a part of another string but as a whole sentence. e.g. “Couldn’t connect.” + “Couldn’t connect. Try again?” – not this, but something along those lines. Painful for translating.
Seems as if iOS 6 could be breaking stats. This is unrelated to WPiOS 3.2 as a release, but something we have to look into asap. Doing support I’ve noticed that quite a few report extreme delays in stats updates in app – it may be because the cache is never cleared.
See this thread: http://ios.forums.wordpress.org/topic/statistics-not-updating
cc @kokejb
It was a caching problem on Safari (iOS6). The issue has been fixed server side.
Testing time!
For folks who can install the latest builds, please take a moment to take our survey and help test out WPiOS 3.2.
Below is a list of devices, OSs and WordPress versions that we need help testing. If you help test, please check off the relevant box so we can get the best coverage.
oSs / Device combos
If you’re testing a particular device let us know here:
Lastly, let us know if you test an older version of WordPress. (Probably testing the minor releases is good enough.)
Thanks!
I tried to build from trunk and can’t get the app to connect to WPcom at all. SIGBART error when tapping the wpcom button in the welcome screen. Sent a few crash reports.
iOS 6.0, iPhone 4S, fresh install.
What about if you install from the build server? Same thing?
It does work if I install from the build server. Why is this? Makes it hard for me to do any work in the app on my own computer 
Maybe check that there’s no local changes in your local repository, and make sure you’re running the latest version of Xcode.
In #1327-ios, I’ve bumped the “required” version to 3.1 instead of 3.0. It’s just a warning, so older sites would still work the same as they did before.
Should we require a higer version? Why not just the latest stable?
Since we’ve traditionally been fairly loose on the restrictions we should gradually move towards it instead. Running an old version of WP is of course a security threat, but we still only need a certain subset of the API that may be available in versions prior to the latest stable.
To avoid backlash from users, I think we should gradually move towards better restrictions. Maybe we could even add an update function in the apps…
We could match it up with Jetpack, I was just testing the app on WP 3.1 and Jetpack showed a “Jetpack requires WordPress version 3.2 or later.” prompt when trying to activate it.
If you’re interested in contributing, this little ticket is a great place to get your hands dirty: http://ios.trac.wordpress.org/ticket/1394
I’ll try and see if I can can figure it out and submit my first patch in next few days
Great!
Sounds for 3.2 update! Attn @jmobb
After discussing the sounds and getting a feel for them in the app over the last few weeks, a few things:
Overall I think we’re very close. Excited to have these go in version 3.2.
Plan for version 3.2 over the next week as discussed in the weekly dev chat:
Ive been looking to get involved, but it is unclear to me where to start. Can you offer any advice?
There needs to be a better getting started guide.
Basically this is how development works for the WP for iOS app:
To create your first patch you should join the weekly meeting and/or ping is in #wordpress-mobile another time to figure out where a good place would be to start based on your obj-c knowledge coming in and of course where your strengths lie in general. After it’s been discussed you get assigned or assign yourself to tickets as needed in Trac and start cranking. Create a patch with the diff and upload that to the ticket and ask someone to review it. If it goes through, you’ll be on the contributors list in the next announcement!
Looking forward to talking more about all this. Is there anything that’s unclear still? Any and all feedback that would’ve helped you get started would probably help others so feedback is much appreciated.
Hi Judy, have you found your way around the app yet?
Updated the milestone due date for version 3.2, aiming for roughly 2 weeks out given that we cut corners and have a beta out sometime next week.
Current stats:
closed: 26 active: 54 Total: 80
Add Blog/Site
4 / 13
Comments
2 / 11
Compose
0 / 2
Media
0 / 6
Notifications
1 / 3
Other
7 / 14
Posts
2 / 8
Publishing
0 / 1
Reader
2 / 6
Settings
4 / 5
Statistics
2 / 2
newui-3.1
2 / 9
Updated the Twitter avatar for @WordPressiOS to match the new app icon introduced in version 3.1, this is what it looks like in context:
Version 3.1.2 is out, fixes login issues for Stats and Jetpack. ow.ly/dbZzK—
WordPress for iOS (@WordPressiOS) August 24, 2012
Brad 2:16 pm on October 16, 2012 Permalink |
Sounds good. So moving towards more of a feature driven development system, should we create new milestones for things like “notifications”, “rich text”, etc?
Isaac Keyet 9:11 pm on October 16, 2012 Permalink |
That could be interesting for sure – why don’t we bring it up in the weekly dev chat and have a discussion?
Isaac Keyet 9:13 pm on October 16, 2012 Permalink |
Let’s propose agenda items in advance like make/core does: http://make.wordpress.org/mobile/2012/10/16/propose-agenda-items-for-the-mobile-weekly-dev/
Isaac Keyet 1:03 am on October 18, 2012 Permalink |
@irbrad was this discussed in the dev chat in more detail? Would be interesting to know what the team thinks of the idea collectively.