View source for Talk:Release checklist not aiming for 1.4

* We're likely to be moving to google code hosting.
* We're also likely to be applying to participate in GHoP.

In the past GHoP has used the google code issue tracker to manage tasks that students are doing.  We are handling our issues in many ways more efficiently than a conventional issue tracker can.  However we do lose out in some respects.

The page [[The Ideal Bugtracker]] describes what I would like to move to in due course.  Once issues are in any system that uses tables we will need short clear titles for each issue.  We will also need to better separate defects form feature requests.  For example.

* Timer Record needs to remember the last scheduled duration 
* Fix: Adjusting the meter update frequency seems to make no difference whatever, whether it is 100, 30 or 1.

The first is a feature request.  The second is a bug.  These would perhaps become:

* '''Remember last duration in Timer Record:''' Timer Record needs to remember the last scheduled duration. 
* '''Meter update frequency has no effect:''' Adjusting the meter update frequency seems to make no difference whatever, whether it is 100, 30 or 1.

So this is just a heads up that we need to be thinking about this.