On Apr 22, 11:25 pm, Simon Cross <hodges...@gmail.com
> I'm coordinating a Bitten sprint this Saturday.
> A group of us are getting together in Cape Town as part of a local PUG
> meeting  but we'll be on #bitten on IRC and we'd be delighted to
> have people from elsewhere join in the ticket stomping. Our local PUG
> meet up should include at least two people with commit access (me and
> davidfraser) and osimons has said he might be on IRC a bit so we
> shouldn't be short on people to commit patches.
> The focus will be on dealing with the outstanding Milestone 0.6
> tickets  but feel free to suggest other tickets for attention.
> I should arrive at the PUG meeting at around 10:00am GMT. Our meetings
> tend to be of somewhat flexible extent but I'm guessing there still be
> a few or us around to push on into the early evening (with perhaps a
> break for dinner at some point).
> If you won't be at the sprint but have something you'd like looked at,
> please file a ticket (and if possible mark it with the 0.6 Milestone
> or assign it to me, i.e. hodgestar).
Thanks Simon, and thanks also to all that participated. Lots of good
patches getting reviewed, adjusted and committed. I'm very impressed
by all the effort put into the project by everyone in just this one
Unfortunately, I did not really manage to follow the sprint and its
discussions and changes. For the most part, you all seemed to have
managed quite well without me - and perhaps even because I wasn't
around :-) Reviewing the code now I just have a few comments and
1) Walter, a great collection of patches included in the sprint. Your
patches are of high quality and I usually never have issues with them,
but let us just say that I would not object if you would tweak your
personal workflow to raise issues and post patches to tickets
2) The new charting still need some work. On first glance it looks
like Lint charting don't work, and I'm seeing errors such as "'dumps'
not being defined" and "'json.txt' template is malformed". That is no
doubt easily fixed, and let us follow details up on the ticket itself
(#426). However, the whole issue that Bitten now requires a json
encoder/decoder is not as clear-cut to me. json module is present in
Python 2.6, and for earlier versions simplejson module must be
installed (requirement). A large part of our users needs to install a
new new module when upgrading. Do we make the requirement explicit in
setup.py, or do we make it optional and just disable all charting if
json is not available? Do we rewire the communication format - like
keep the pre-existing XML format and instead reformat it to json on
the client before plugging it into graphs? I'm not quite sure what was
has been discussed.
Again, a big thanks to all that participated!