Hi again Vlad,

Below is an update of the 1.2 review.

In short, the missing parts for the completion are :

   - 4 bugs to fix : 601603, 610733, 612470, 623446
   - update file
   - release note file
   - AjaxIM

This list is still pending some testing from Xav (especially the parts that
I could not perform such as simpletest) but this is what I have so far.

I have an issue - it's that I don't usually release a payment while the
milestone is not complete. But I know that this milestone is pending for
some time, that AjaxIM is more tricky than expected, and that it might put
you in a complicated position.
So what I can offer is to release half of the paiement for 1.2 when all
points except AjaxIM are fixed, and release the 50% remaining once we have a
solution for AjaxIM. What do you think ?

For the next iterations, I suggest that when there is a feature you (or any
contractor) are not completely sure can be delivered on time, you do a
little research before the iteration starts so that you can identify and
communicate the risks to us , and then we can plan in advance the case where
the feature cannot be delivered on time (typically our current situation) -
do you think it's possible ?

When do you think you can fix the first part (all points except AjaxIM) ?

For the 2.0, can we shedule the end of it for next iteration, i.e. next
thursday ? The idea, in order to be able to validate the 2.0 when it's
released even if Ajaxim is not solved then, would be to use a placeholder in
the mission system that replaces ajaxim until the issue is fixed, so that we
can test the functionalities of the mission system even without ajaxim.
Doable ?

Thx
David



  Step Description Status Comment  *1* Merge developer branch (*bzr merge
lp:xxx*) OK
 Done
  *2* Follow update procedure (described in UPDATE file) *NOK*
 could not find UPDATE file
  *3* Tests: simpletest & JSCoverage at 100% and without error for all new
code (+check that new files are taken into account) pending

   - simpletest : could not generate report locally
   - jscoverage -> 97%

  *4* Tests: Windmill tests run without error (run all & verify created for
new features) OK
 All tests pass fine  *5* QA: Test release changes (compare with specs) *NOK
*

   - Leaderboard : add rank to bar. OK
   - Leaderboard : show elements following a successful task. OK
   - Leaderboard : add proportions. OK
   - Leaderboard : display. OK
   - Leaderboard : link in option. OK
   - List of websites :Integration. OK
   - List of websites : Changes since last session. OK
   - Missions : NOK
   Not on my local branch yet

  *6* QA: Browser compatibility (IE 6-7-8, Firefox 2-3, Safari, Chrome,
Opera) *NOK*

   - tested on Firefox 3.3. OK
   - tested on Chromium 5 OK
   - tested on Opera 10 OK
   - tested on Safari 5 OK
   - tested on IE 6 NOK (bug 612470)
   - tested on IE 7 OK (there is a pop-up message of script error but it
   still works fine)
   - tested on IE 8 OK (there is a pop-up message of script error but it
   still works fine)

  *7* Code review: Read code <https://code.launchpad.net/hackit> for each
change & comment  ? [Xav]
  *8* Code review: Check other deliverable
requirements<http://community.hackit.cx/wiki/Requirements_and_deliverables_for_patch_submission>(documentation,
OO, commit isolation...)
 ?
 [Xav]
  *9* Bugtracker <https://bugs.launchpad.net/hackit>: Check fixed bugs (open
bugs for this release must all be in Confirmed state at the end) *NOK*
 The following 4 bugs need to be fixed : 601603, 610733, 612470, 623446  *10
* Check & publish release
notes<http://community.hackit.cx/wiki/Requirements_and_deliverables_for_patch_submission#Release_notes>
*NOK*
 Could not find release note
  *11*

Commit & push
 *NOK*
_______________________________________________
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

Reply via email to