- WP Android Status
- WP iOS Status
- Other platforms
- Google Summer of Code 2014
- Team Reps
- This Week
- iOS Status
- Android Status
- Team Rep
- This Week
Last week we released 3.9 debuting the app’s new tabbed interface, including lots of optimization and bug fixes.
Since its release we’ve become aware of a handful of bugs including one regarding a post’s publish date, and one where the app forgets the last viewed tab when reopening.
We’re currently focused on getting 3.9.1 released to address these urgent issues and expect to submit to Apple later this week.
We released 2.6 last Thursday. There are a handful of bugs (about 10 exceptions) we’re working on for a 2.6.1 release later this week.
Last week we acknowledged we were due to re-up our team reps and we called for volunteers. @irbrad and @astralbodies have both expressed interest and will be taking the reigns as reps for the mobile team going forward. Congrats guys!
iOS: Complete fixes for 3.9.1 and submit to Apple. Begin work on 3.9.2.
Android: Complete fixes for 2.6.1 and release to the Play store.
Next Dev Chat
The next dev chat will be held at 17:00 UTC on Feb 10 in #wordpress-mobile on Freenode.
Hey Mobile Team! Guess what. We’re overdue to elect new team reps.
For those of you who aren’t familiar with the role of a team rep, it largely focuses on communication, being a point of contact for other WordPress teams, and keeping other teams up to date with what what we’re up to. You can read all about it or just ask if you have questions. 🙂
For this round of elections, let’s do a PollDaddy poll like we did the first time round. If you’d like to throw your hat in the ring, just leave a comment here saying so. This Friday we’ll vote via PollDaddy poll and choose the reps for the next three months.
Chime in if you have any questions or comments. 🙂
Delayed summary of what went down yesterday for the record. Chat log.
- iOS Status
- Android Status
- Handbook Update
- Team Reps
- What’s Next
3.7 with the new WordPress.com Reader and a new account system launched (woo!) but had some serious bugs, including a launch on startup for some due to migration issues (boo!) so we’ve been hard at work trying to fix the issues. A .1 will be pushed asap. Next up is a .2 with some minor enhancements.
2.4.4 was just pushed to Google Play and includes some enhancements like Picasa/Google+ image uploading/adding and post excerpts — props @aagam94!
Later this week we’ll launch a beta with theme selection and media library enhancements. We’re also starting the new user experience iteration back up (better log in/sign up and welcome guide).
We talked about electing new team reps. Since our group is very small we decided to keep it simple and elect new reps in the chat itself. @irbrad was up for a term but not this time around, so for now @aerych and @isaackeyet will continue being team reps without specific primary/secondary roles (we’ve switched from week to week up until now and it has worked well). Worth noting is that the new cycle is 3 months for a handoff between primary/secondary team reps but since it’s worked so well I think we can continue on as we have and fill in for each other when necessary.
iOS: fix the bug in 3.7 asap and issue 3.7.1, then start working on 3.7.2. iOS7-ification is also under way, as is the code clean up and partial refactor, both in separate branches for now.
Android: Media/Themes beta and NUX (welcome guide, improved log in/sign up) is next, along with the Android WordPress.com Native Reader project.
We discussed bug tracking briefly and decided to track issues with the iOS app directly on Github using Issues — this will be adopted by the Android app shortly as well.
We also talked about using Hockey app for Android beta distribution. We concluded that we should explore more to see how feasible it would be and maybe start a post on this p2 about it.
Join us for the next dev chat on Aug 26, 2013 at 16:00 UTC. Mark your calendar and join us in #wordpress-mobile on Freenode.
Its been [over] six months since team reps were selected and its time again to choose. For anyone unfamiliar with the role of a team rep, responsibilities focus around communication and keeping the other teams up-to-date with what’s happening in our mobile world. Check out this page for more info.
The last time, we asked for folks who were interested in the team rep role to identify by leaving a comment, then we voted via a PollDaddy survey. That process seemed to work pretty well, and we do that again if that’s what everyone prefers, but I wondered if it might be simpler if we just decided during the weekly dev chat, since we’re a pretty small team.
So if its alright with everyone, let’s ask folks who are interested in taking on the role of a team rep to announce themselves in a comment below and we’ll plan on making a group decision during the dev chat on Monday. (Of course we can always setup a PollDaddy survey if folks would rather.)
5 people voted, all of whom say they contribute currently to the mobile apps.
Isaac is the 1st rep, and Eric is the 2nd. Congrats! The new term starts with the new year, so I’ll be in touch re expectations.
Time to vote for team reps! When we started formalizing contributor groups we tapped Isaac Keyet as the acting rep for this team, but it’s time for semi-annual elections. You get to vote for 2 team reps. These folks will be responsible for reporting on the progress of the group to the other team reps via weekly updates, as well as occasional chats and such. If you haven’t seen the spiel on one of the other team blogs about how team reps/voting/terms work, the longer explanation is after the jump.
Note: It should be folks who want the responsibility. Anyone interested in being a mobile team rep should leave a comment saying as much so people know who they can/should vote for. Voting is open until December 15, and results will be posted here once voting closes.