Bugfix release?



    Since Maxima is moving from one person being in charge of
    most things to something more distributed, I suggest that we
    do a few things before answering the question.

    - Make an educated guess at the number of people with coding
      skills that would contribute to development.  Did anyone
      make count last time the questions went out?

    - Make an educated guess at the number of people with
      software development administration skills that would
      contribute to development.  I don't recall this skill-set
      being addressed here before.

    - Make an educated guess at the number of people that could
      test, package, distribute, document.

    - Find another nicely running open source project of about
      the same size, and see what they're doing that works, then
      copy everything that's applicable.

    I'd like to just answer the question, but I'm on a very small
    development team (only four of us, two as administrators, all
    four as developers) which runs through sourceforge.  I don't
    know that our model is applicable, though it might be if the
    number of developers, administrators, and other contributors
    turns out to be that small.

    Comments?

On 12 October 2001 at 11:59, Raymond Toy <toy@rtp.ericsson.se> wrote:

Either
1.  Give some people write-access to the CVS files in U Texas.
2.  Move them to the maxima sourceforge site and give selected people
    write-access to those files.
3.  Some other solution.

To get things rolling, I volunteer to test patches, etc, and to commit
them to CVS if people feel I'm so qualified.  I do not, however, want
to take the responsibility of a "release", except, perhaps, bundling
up the files into a tar file and waving a magic wand over it,
chanting, "Release". :-)