http://wiki.mipt.ru/index.php?action=history&feed=atom&title=Development%3AiPhone_App_Development_Process 2026-05-08T02:42:45Z История изменений этой страницы в вики MediaWiki 1.42.1 http://wiki.mipt.ru/index.php?title=Development:iPhone_App_Development_Process&diff=12254&oldid=prev 2024-10-21T08:59:26Z

<p>1 версия импортирована</p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <tr class="diff-title" lang="ru"> <td colspan="1" style="background-color: #fff; color: #202122; text-align: center;">← Предыдущая версия</td> <td colspan="1" style="background-color: #fff; color: #202122; text-align: center;">Версия от 08:59, 21 октября 2024</td> </tr><tr><td colspan="2" class="diff-notice" lang="ru"><div class="mw-diff-empty">(нет различий)</div> </td></tr></table>

Олег Давидович http://wiki.mipt.ru/index.php?title=Development:iPhone_App_Development_Process&diff=12253&oldid=prev 2011-03-17T03:36:07Z

<p></p> <p><b>Новая страница</b></p><div>This document is destinated to Moodle HQ people. It is a micro development process for a team of two developers and 1 &quot;client&quot; (Martin).<br /> <br /> == Set up your environment ==<br /> You need to have a HQ cvs account for developing the Moodle App.<br /> <br /> === Clone the app === <br /> The first thing you need is to retrieve the code from Git:<br /> <br /> &lt;code&gt;<br /> git clone ssh://yourusername@git.moodle.org/git/moodlehq.git ./your_working_folder<br /> &lt;/code&gt;<br /> <br /> === Install Xcode ===<br /> Go on http://developer.apple.com/technologies/tools/whats-new.html and download xcode<br /> <br /> === Setup your iPhone for real testing ===<br /> Go on https://developer.apple.com/ios/manage/overview/index.action and follow the instruction.<br /> You should be able to launch Xcode4, open the Moodle project and run it on your iPhone device.<br /> <br /> == Friday avo: iPhone sprint meeting ==<br /> Every Friday, beginning of avo, we go through:<br /> * resolved issues (they should be already in master branch)<br /> * new assignments by priority, for a week of work maximum. Everything that can not be done in the week stay assigned to the client.<br /> * talk about required task and new features =&gt; create new issues, assigned by default to the client.<br /> <br /> == Week work ==<br /> === Work on your assigned issue ===<br /> Resolve your issue by priority. If there is no specification for the issue and it concerns some news functionalities (it is most likely going to be the case), &#039;&#039;&#039;you must write some functional and technical specifications before coding&#039;&#039;&#039; in Moodledocs. It is really recommended to add Mockups.<br /> <br /> === Share your work in the repository ===<br /> &#039;&#039;&#039;Everytime you resolve a tracker issue&#039;&#039;&#039;, you must push your code into master branch. So your team mate and the client can access it, test it, detect issue.<br /> Then always assign your team mate as QA tester.<br /> <br /> == Friday morning: testing ==<br /> If you have any QA issue left to test, it must be done before the meeting.<br /> <br /> == Flexibility ==<br /> You are allowed to assign another issue to yourself, create new one, and work on them. You can test whenever you want, write specification whenever you want... However try your best to reach the Friday Sprint assignments before the next meeting.</div>

1>Jmouneyrac