' ... when there's something big enough that really needs to be out there fast, then we start to think about when we're going to compile a release. We're due to do a compile today. ... We don't do one for each time because we'd be doing it every day. As I say if something big comes along which needs to be fixed then that would definitely mean that we'd release it otherwise things build up until, you know, we get sufficient amount to warrant a release. ... At the start they were going out..the first week about two went out, then they were going out about weekly, now they're going about fortnightly, maybe a little longer since than the last one. ...X043 page 001.05c (tape 06.2.02) Alan Notes/Tape 14/06/94I think we were a little bit too quick to solve things for people, not necessarily serious bugs, but we don't like this like this or just change that and the users were starting to get used to the idea that we could change things overnight and they were starting to have things a little too whimsical at that stage. So I was quite keen when I took over not to just do everything they want when they want it. To try and be a bit structured about it. So that's why I've held on with this one. But now, Len has been working on a new report for the system, two new reports which the service handlers down in Essex are particularly keen to have and he's just about finished that, ... He's testing that now so it's a logical time to do a release when this is ready. It's actually going out in a test form. We're not saying it's live as such. It will be in the system but it's got test written on it and we've explained to the people who will be using it that for the first couple of weeks we treating it as a test feature.'
Social influence: | |
Technical influence: | Tasks: Maintenance |
![]() |
Recording |
![]() |
![]() |
Story |
![]() |
Social influence | ||
![]() |
Technical influence |
![]() |
© Clare Tagg 2000