On Wed, 2010-07-28 at 08:17 +0200, Xavier Antoviaque wrote:
> 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
> )
Updated. There is still the browser compatibility tests to do - anyone
wants to help? It's basically just a matter of installing the different
version of the browsers we support, and testing the game to make sure it
works correctly.
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)
OK
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
OK
* Good start
on the
OO-programming. Still some work to do, but nice job laying down the
ground.
* There will
still be
work to do
to get a
full OO
structure
- to
encapsulate things like player, levels, etc. This can be spread
progressively over the next releases though.
* The first
thing will
be to
ensure
that code
accessing
SQL data
structure
is
encapsulated in the corresponding object - cf for example function
get_play_data()
* db_hackit_2010.07.27.sql & db_hackit_test_2010.07.27.sql - shouldn't be
renamed at every change, to keep the file's modification history
* We'll need
to change
the
copyright
from
Politis
Games to
Farsides -
I've
created a
bug
report,
I'll
affect it
to a
future
release
8
Code review: Check
other deliverable
requirements
(documentation,
OO, commit
isolation...)
OK
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
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
