|
|
| (6 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| == 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 == | | == 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
| | Moodle Mobile version numbers consist of three numbers separated by a dot, for example 1.3.2 or 1.4.4. The first two numbers, like 1.3, represent the major version. The third number distinguishes minor versions within the same major 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)
| | === Major and minor versions === |
|
| |
|
| Since MoodleMobile depends on WebServices created in Moodle, new MoodleMobile features must be synced with new Moodle WebServices that are usually present in Moodle major releases.
| | * Major version includes new features and improvements. |
|
| |
|
| For this reason there will be some MoodleMobile major versions that will not add functionalities for working directly with Moodle (reading or sending data):
| | * Minor version includes only bug fixes. |
|
| |
|
| 1.3 July 2013 - Major MoodleMobile release not adding functionalities directly related to Moodle
| | The current release cycle is one version per month (in the first two weeks of every month) |
| 1.4 September 2013 - Same, new functionalities that no rely on Moodle WebServices
| |
| 1.5 November 2013 . Major release adding new functionalities that relies on Moodle WebServices (may be; forums, notes, grades...) due to Moodle 2.6 is released also in November 2013
| |
|
| |
|
| == See also == | | == See also == |
Versions
Moodle Mobile version numbers consist of three numbers separated by a dot, for example 1.3.2 or 1.4.4. The first two numbers, like 1.3, represent the major version. The third number distinguishes minor versions within the same major version.
Major and minor versions
- Major version includes new features and improvements.
- Minor version includes only bug fixes.
The current release cycle is one version per month (in the first two weeks of every month)
See also
Moodle Mobile Release Notes
