Mobile dev chat summary for Nov 21, 2012

Chat log.


  • WPiOS
  • WPWindowsPhone
  • Make/mobile changes and migrations
  • TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub. guidelines for feature driven development
  • Mobile Handbook


Sounds release (should be v 3.3):
Ready to go, asking for some final feedback on the sounds on Twitter and in the forums.

Notifications release:
No update, but development is progressing.


1.7 (Local drafts, Windows Phone 8 support):
Complications when submitting, the update doesn’t work as expected for Windows Phone 8 devices. We’re in touch with Microsoft to help resolve the issues, but can only wait right now. Announcement pending.

1.7.1 bugfix update is pretty much ready to go.

1.8 (Moderation and Comments):
Work is progressing. If everything goes well we’ll submit early next week (shooting for Monday), but depends on when we can push the 1.7 and 1.7.1 releases through.

Make/mobile changes and migrations

Just a heads up: over the next few weeks we’ll work on moving all the dev blogs, app sites, public blogs, and forums/support over to The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. This will happen gradually starting with the simple bits (like moving all the /development pages on the various sites) to one central location (most likely on this blog or in the upcoming Mobile Handbook).

Trac guidelines for feature based development

We spent a good chunk of time discussing how we should go about feature-driven development in Trac (full log here). In the end we concluded the following:

  • Milestones should be based on features and not versions.
  • Bugs fixed should be tagged with the Next Release milestone, and then migrated over when a feature is ready to be submitted/released.
  • Bugs that need to be curated with a feature release are the only types of defects that should be tagged with a specific feature release.
  • After every major app update has been submitted, we’ve now made it the norm for the team working on that update to spend the time in between submitting to the app being approved to go on a bug hunt in Trac, as well as keep testing the release and fix any issues.

Feature-driven development enables us to iterate faster and quickly submit app updates when a particular feature or set of enhancements are ready. Any new feature or major enhancement means a version number bump (e.g. 3.X).

We acknowledged the overwhelming amount of “defect” type tickets especially in the WPiOS Trac and recognized that something has to be done about this to build sustainable, bug-free apps. The steps above are intended to deal with this.

Mobile Handbook

Some concerns were brought up as to what the Mobile Handbook would contain. To the best of our knowledge, the Mobile Handbook would have a bit of the same content as the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Handbook. We acknowledged the guidelines already posted, and that the Mobile Handbook would need at least in part specific sections for each app (because the platforms and how you develop on them are so different). We’ll also want to mention that the apps are on GITGit Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. Git is easy to learn and has a tiny footprint with lightning fast performance. Most modern plugin and theme development is being done with this version control system. as well as SVNSVN Apache Subversion (often abbreviated SVN, after its command name svn) is a software versioning and revision control system. Software developers use Subversion to maintain current and historical versions of files such as source code, web pages, and documentation. Its goal is to be a mostly compatible successor to the widely used Concurrent Versions System (CVS). WordPress core and the released code are all centrally managed through SVN. As previously noted, mrroundhill, koke, and daniloercoli will help write it as the lead developers for their respective platforms. Jkudish mentioned in the chat that he’d be up for providing some pointers for us as he recently got started with mobile development himself.

Next chat

Join us for the next weekly chat Wednesday at 1600 UTC on in the #WordPress-Mobile room.