[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Weekly report week 36, plans for week 37



> plans for week 36:
> - release a new wlus

check

> - work on the testsuite

check.  this went slow. i ran into a few blocking problems: the
HTTP::Recorder (which i wanted to use to build a framework for
normal users so that they could produce a testcase to bugs they
encountered) did not work with https and once i got it to work
with http, it did not work properly, either. i guess it could
best be used as a programming aid for developers, taking some
boring code generation off of their hands.  Then the user mode
linux environment came down with a couple of funny errors. i
found a patch and promply ran into more bugs in uml, which first
looked like rootstrap bugs. The first level support (debian
maintainer, mdz) could not help me. still waiting for replies to
my help!-mail to the upstream author.

> - extent the small programming jobs to include the css project

not done that yet, looked at css in more detail instead.

> - compile a new kernel for my workstation to be able to use
>   afs on it and debug the usb subsystem, which dies regularly.

check

furthermore i
- supported Patrick in his effords to add password hashes
  to wlus' fileimport.
- found and fixed a wlus bug discovered by Klaus.
- sent off a couple of bills to Markus.
- got very important major debconf5 stuff sorted out
- wrote a whole lot of mail on various subjects regardeing
  debian-edu. (Sam Hartmann, the afs maintainer, is very open and
  positive about debconf pre-seeding, for example)

This week (37) i will continue to work on the test framework.  In
contrast to last week i will avoid trying to find bugs in other
peoples code but instead produce more myself. ... code, that is.

i will also release a new wlus.



Reply to: