http://wiki.mipt.ru/index.php?action=history&feed=atom&title=Development%3AWeekly_Code_Review 2026-05-06T17:38:21Z История изменений этой страницы в вики MediaWiki 1.42.1 http://wiki.mipt.ru/index.php?title=Development:Weekly_Code_Review&diff=12154&oldid=prev 2024-10-21T08:59:19Z

<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:Weekly_Code_Review&diff=12153&oldid=prev 2011-04-28T11:52:14Z

<p><span dir="auto"><span class="autocomment">See also link</span></span></p> <p><b>Новая страница</b></p><div>Moodle has a weekly process of code review in the stable branches to help improve the quality of stable packages and to help detect any regressions that may have occurred in stable code.<br /> <br /> Here is the process for testers and developers:<br /> <br /> ==Every Tuesday==<br /> <br /> ===Don&#039;t check any new fixes into CVS===<br /> <br /> HEAD is OK, but please avoid new fixes in all STABLE branches unless they are definitely definitely not going to cause new bugs ;-)<br /> <br /> ===Find bugs to test===<br /> <br /> All developers and testers should be looking at:<br /> <br /> Moodle 1.9 stable: [http://tracker.moodle.org/secure/IssueNavigator.jspa?mode=hide&amp;requestId=10565 1.9.x Needs QA review]<br /> <br /> (Make sure you can see the QA Assigned column)<br /> <br /> Grab any bug that:<br /> <br /> * Is from the last week<br /> * You did not fix<br /> * Does not have a QA assignee yet <br /> <br /> and claim it by editing the bug to add your name as QA Assignee.<br /> <br /> ===Test the fix===<br /> <br /> * Read the comments <br /> * Look at the patch attached to the tracker<br /> * Try the feature out to make sure it works as advertised <br /> ** Ensure you have debugging set to the DEBUG_DEVELOPER &amp; look for new errors<br /> ** Test for potential regressions in other areas the fix may affect<br /> * Post new comments (or talk on Moodle HQ) if you need clarification<br /> <br /> ===Deal with any problems===<br /> <br /> * Post a comment on the bug with details (preferably including patch!)<br /> * Reopen the bug<br /> * If it looks like the original developer isn&#039;t seeing it, reassign to Eloy Lafuente for [[Development:Bug triage|triage]]<br /> * If the fix is obvious and you have CVS access, fix it yourself<br /> <br /> ===Mark the fix as reviewed===<br /> <br /> * When you are satisfied the bug is correctly fixed, simply change the status from Resolved to Closed<br /> * If you committed any fix, let somebody else review it again - do not Close it yourself<br /> <br /> ==Every Wednesday==<br /> <br /> * The download site will automatically tag the whole current stable codebase (e.g. MOODLE_19_WEEKLY) at 1:00 GMT on Wednesday morning and then build download packages<br /> <br /> ==See also==<br /> <br /> *Using Moodle [http://moodle.org/mod/forum/discuss.php?d=93474 Tuesday Code Reviews] forum discussion<br /> *[[Development:Process]]<br /> <br /> [[Category:Developer|Weekly Code Review]]<br /> [[Category:Quality Assurance]]</div>

1>Libertymoodle