Mail Archives: djgpp-workers/2002/06/15/13:37:23
> Date: Thu, 13 Jun 2002 16:24:18 +0100
> From: Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>
>
> What exactly is involved in managing the release?
Making the *.zip files and uploading them to DJ's server, tracking
after bug reports during beta testing and checking in fixes. That's
about it, but don't let this short list dupe you into thinking it's an
easy job, or that it won't take a significant portion of your time.
> * Review everything that's changed between 2.03 and 2.04 and formulate tests
> for the new functionality and to check that nothing's broken.
That's not in the job description: testing the release is the job of
people who participate in the alpha and beta testing stages. You are
just one of them, but you don't need to do this all by yorself.
> * Build lots of software using the release, to see if it breaks anything.
This is also not the responsibility of the release manager: all
pretesters are collectively doing this. The manager just gathers bug
reports, and if they end up pointing to djdev bugs, fixes them and
checks in the changes.
> Can you estimate how much time it takes roughly per week to be the "release
> manager"?
It depends on how frequent does one make new pretest releases
(normally should be once in a few weeks), and how many bugs will ne
reported. In other words, cannot really say.
> <Shouts "Geronimo!"> I'm thinking of, er, volunteering. 8)
Thanks!
- Raw text -