Codespeed 0.8 and future plans
Miquel Torres
there is a lot going on in the Codespeed community and to easy further
development, I am releasing Codespeed 0.8. Changes can be found at the
wiki https://github.com/tobami/codespeed/wiki/Releases or in the
changelog file.
Be forewarned that due to the merging of refactoring code over the
last months, most notably Danilo's "branches", there may be more bugs
than usual.
Code Clean-ups
=============
Chris Adams has done a lot of code clean ups, some of which, but not
all, already appeared in the 0.7 release. He also implemented VC
integration for github, and a command line client to save results via
HTTP.
Branches
=======
Branches change the DB schema. Before we had:
Project => Revision => Result
now:
Project => Branch => Revision => Result
The aim of the branch feature is to be able to compare results for
feature branches before they get merged back into master. "default" is
the default branch, which should be used for "trunk", "master", "tip",
or whatever the main branch is called. Branches other than "default"
will be shown in the Comparison view, but nowhere else. Nothing
prevents us from adding branches to the timeline view in the future.
Migration
=======
It is possible to convert a database from 0.7 into 0.8, following the
instructions found in the wiki page:
https://github.com/tobami/codespeed/wiki/How-to-migrate-DB-schema-to-0.8
Danilo also managed to improve multi project support by grouping
executables by project in the comparison view. Timeline should get the
same treatment in the future.
Documentation
============
Another great contribution was made by David Fraser, who wrote new
documentation (documentation/intro.wiki) explaining the Codespeed
views and concepts. It can also be found in the Wiki:
https://github.com/tobami/codespeed/wiki/Overview
Future plans
=========
a8 has (re)implemented Codespeed as a proper Django app, which should
solve things like url handling and install-ability among others. The
aim is to merge his fork first, stabilize, and dedicate the 0.9 and
0.10 release cycle to several features:
* Danilo is now working on his GSoC (we got accepted, yeah!). His
goals are the implementation of several statistics features (error
bars, for example), and of multi project support. You can find more
about the GSoC here:
https://github.com/tobami/codespeed/wiki/GSoC-Draft
* Chris multi-project, multi-url work
* RESTful API
* installability: PyPI, Chef recipe, etc.
* Authentication for POSTing
* Discuss recent feedback (specially Chuck's) to improve the UI and
performance for data with lots of parameters.
If possible I would prefer to release a quick 0.9 that adds polish and
improves many-parameter use-cases, and release features that take
longer with 0.10.
Thoughts, ideas?
Miquel
Danilo Freitas
:)
I guess we should work a lot on bugfixes for 0.9, as we got some bugs
with the branch merge.
Is there something like a buglist or a trac?
Miquel, when do you plan to release? If it's after July, I can work
better fixing these bugs.
2011/6/21 Miquel Torres <tob...@googlemail.com>:
--
Danilo Araújo Freitas
PaintCode Software @paintcode
Miquel Torres
Well, I've been lately posting links to issues left and right ;-)
https://github.com/tobami/codespeed/issues
> Miquel, when do you plan to release? If it's after July, I can work
> better fixing these bugs.
I don't plan any particular date. It can be a feature based release,
with a focus on fixing and polishing, and when we feel like it is an
improvement we can release.
2011/6/22 Danilo Freitas <dsur...@gmail.com>: