|
|
| Line 2: |
Line 2: |
|
| |
|
| == Team == | | == Team == |
| Moodle Mobile is developed by a small team of three persons: | | Moodle Mobile is developed by a small team of these persons: |
|
| |
|
| * Juan Leyva (Lead developer) | | * Juan Leyva (Lead developer) |
| * Laia Canet (Users advocate, UIX and documentation support) | | * Barbara Ramiro (CSS, layout) |
| * 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 August we may publish 1.3.1 (maintenance release only fixing bugs, no new features) and in September we will publish 1.4 (hopefully)
| |
| | |
| === Releases that rely on new Moodle 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.
| |
| | |
| For this reason there will be some MoodleMobile major versions that will not add functionalities for working directly with Moodle (reading or sending data):
| |
| | |
| * 1.3 - July 2013 - Major MoodleMobile release not adding functionalities directly related to Moodle
| |
| * 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
| |
| | |
| Any new release will be able to work with Moodle 2.4 and onwards, but only features only available for Moodle versions higher that your current site one will not be displayed in the app. The app will be able to detect which features can be used depending on your moodle remote site.
| |
|
| |
|
| == See also == | | == See also == |
