On Tue, 2010-07-27 at 23:19 +0200, Xavier Antoviaque wrote: > > I'll resume the work tomorrow morning and give you the details.
Here it is. I've made a checklist for release acceptance (cf http://community.hackit.cx/wiki/Alpha1_Usability_Improvements#Requirements_and_deliverables ) Step Description Status Comment 1 Merge developer branch (bzr merge lp:xxx) OK Resolved conflict in config.php.dist (DOS mode) 2 Follow update procedure (described in UPDATE file) NEW Not expected for this release 3 Tests: simpletest & JSCoverage at 100% and without error for all new code (+check that new files are taken into account) OK Remains a few untested lines from alpha1.0, to be fixed on next review by Proppy 4 Tests: Windmill tests run without error (run all & verify created for new features) OK Will need more tests in future releases, but existing tests work 5 QA: Test release changes (compare with specs) NOK Only minor issues - see bugtracker 6 QA: Browser compatibility (IE 6-7-8, Firefox 2-3, Safari, Chrome, Opera) TODO Not tested yet 7 Code review: Read code for each change & comment TODO Not tested yet 8 Code review: Check other deliverable requirements (documentation, OO, commit isolation...) NOK Code documentation is not complete and commits haven't been properly isolated (though it's too late to fix the later) 9 Bugtracker: Check fixed bugs (open bugs for this release must all be in Confirmed state at the end) NOK Still some pending bug tickets open 10 Check & publish release notes NEW Not expected for this release 11 Commit & push TODO Done, but need to wait final release I still need to review the code itself and make the browser compatibility tests, but this give you things tp fix already. Btw, about code reviews - one big commit isn't very easy to read - I've updated the requirements to make it easier next time: Requirements: http://community.hackit.cx/wiki/Requirements_and_deliverables_for_patch_submission Diff: http://community.hackit.cx/index.php?title=Requirements_and_deliverables_for_patch_submission&diff=2105&oldid=1750 I've also described the current release cycle, and gave fixed days to start & end a cycle (it will help me to end a cycle on Thursday - this way I have the whole Friday free to do the acceptance work). If it's ok for you and David, we could use it for alpha1.2, and start the next iteration on Friday. http://community.hackit.cx/wiki/Development_Cycle Also, are you ok to start working on a new release immediately after submitting one? For example, here, it would mean fixing issues with alpha1.1 the same week as working on alpha1.2 (ie having week+1 for alpha1.1 at the same time as week 0 for alpha1.2). Xavier.
_______________________________________________ Hackit Bar mailing list - [email protected] Wiki: http://community.hackit.cx/ List: http://community.hackit.cx/ml/ Forum: http://community.hackit.cx/forum/ Ideas: http://community.hackit.cx/ideas/ IRC: irc://irc.freenode.net/#politis
