Log in

No account? Create an account
Weekend? What Weekend? - Sam's Journal

> Recent Entries
> Archive
> Friends
> Profile

My Games
Web Cam

September 10th, 2006

Previous Entry Share Next Entry
08:07 am - Weekend? What Weekend?
I guess the official release crunch is now on. On Thursday, the VP of Engineering "asked" us to work weekends until our release is complete. We're already a week behind the schedule that was set by Marketing edict; gosh, I wonder why we're behind schedule?

So that means I'm going in today as well. Yesterday we wrapped up a build that had all test blockers "fixed", but there's still a nice pile of other bugs to address. Bugs, mind you, that have been in every single release of our code until now, bugs that weren't specifically added to this release, but that people now insist are "must fixes" for the release.

There are many little aggravations in this release; for me, one of them is the (lack of) bug tracking process. It's not that we don't track bugs, bug I dislike HOW it is being done. One observed defect = one bug, to me. But our testers love to load a single bug report with 4 or 5 different "issues", which are often entirely different issues. It's just something that I think makes the development team's job harder.

Now to forget about work for a little while longer...
Current Mood: blahblah

(2 comments | Touch Me)


[User Picture]
Date:September 10th, 2006 03:36 pm (UTC)
We try to write up 1 bug per change request (our equivalent) because I think otherwise not everything ends up going to the correct developer because 1 person is assigned to fixed 1 bug, because it makes the database hard to query/keep organized if you dump a lot of issues into one and because it makes it difficult for everyone to track the status. I actually felt really bad recently when I wrote up 3 seemingly related things up as 1 bug and Kim worked on it, returned it, but when I tested it, it was only 2/3 fixed.
[User Picture]
Date:September 10th, 2006 10:53 pm (UTC)
I think I'm slowly winning our test team over to the "file multiple bugs for multiple observations" concept; the test lead was worried that it would inflate our bug numbers and make it look like we're not going to make release but slowly seems to be giving on.

But, then, so far today I've identified 3 more "bugs" that are actually dupes of fixed problems; they just hadn't been marked as "fixed" because they were down the priority list and, therefore, we hadn't even looked at them. Yay for the appearance of productivity! *snicker*

> Go to Top