Difference between revisions of "Moodle Mobile Development Process"

Jump to: navigation, search
(Releases)
(Versions)
Line 13: Line 13:
 
For achieve this we organize the code using a Control Version System called git where we track two "branches" of code called:
 
For achieve this we organize the code using a Control Version System called git where we track two "branches" of code called:
 
* master - Branch for the code of new versions
 
* master - Branch for the code of new versions
* MOODLEMOBILE_XY_STABLE - Branch for maintain the code of the current published version
+
* MOODLEMOBILE_XY_STABLE - Branch for maintain the code of the current published version, fixing bugs (not adding improvements or new features)
  
 
Every time we publish a new version (i.e: 1.4) we create a MOODLEMOBILE_XY_STABLE branch (MOODLEMOBILE_14_STABLE in this case) for maintaining this version until we release a new version; old branches are keeped as historic but we don't work on it.  
 
Every time we publish a new version (i.e: 1.4) we create a MOODLEMOBILE_XY_STABLE branch (MOODLEMOBILE_14_STABLE in this case) for maintaining this version until we release a new version; old branches are keeped as historic but we don't work on it.  

Revision as of 09:38, 14 June 2013

Team

Moodle Mobile is developed by a small team of three persons:

  • Juan Leyva (Lead developer)
  • Laia Canet (Users advocate, UIX and documentation support)
  • Josep Maria Gifreu (CSS, layout)

Versions

The development process is oriented to:

  • Maintain the current published version free of bugs
  • Add new functionalities for future versions

For achieve this we organize the code using a Control Version System called git where we track two "branches" of code called:

  • master - Branch for the code of new versions
  • MOODLEMOBILE_XY_STABLE - Branch for maintain the code of the current published version, fixing bugs (not adding improvements or new features)

Every time we publish a new version (i.e: 1.4) we create a MOODLEMOBILE_XY_STABLE branch (MOODLEMOBILE_14_STABLE in this case) for maintaining this version until we release a new version; old branches are keeped as historic but we don't work on it.

It doesn't makes sense maintain old versions because the way they are handled in Mobile markets (you can only upgrade to last version of an app)

Releases

The plan is release a new major version (1.X) every two months and minor versions/maintenance (1.X.Y) at any time when needed

I.e: In July we release 1.3 (major version). Once 1.3 is published we will start working in version 1.4 and meanwhile we will be fixing bugs for the 1.3 version

In Augusts we may publish 1.3.1 (maintenance release only fixing bugs, no new features) and in September we will publish 1.4 (hopefully)