hi all.
now that the gem-0.90 release is out for some weeks, i think it is time to start some traffic on this list again. (but of course: what to talk about now ? we used to discuss the release for years...)
some points:
------- stable: i have branched v0_90 for bug-fixes on the latest stable release
-------------------- further development: wini has done some research on opensource-development and has found out that os-dev can be organized effectively in (surprise:) several ways to achieve an optimum development/stability-ratio: (the following is a translation from german and it is already some weeks ago, so i might use the wrong termini)
a) pope: one person revises all code and decides which parts of the development should go into the next release b) committee: a small team off people does like the pope. c) branching: each new feature is branched off the main CVS-trunk. as soon as it has become stable the branch is merged with the main trunk.
i don't think that a) would be a very good idea (as it has proven to lead to major quarrels and misunderstanding) as for b) it seems like a bit of an overhead, as the core-development team is so small, that all of us would be in the committee.
so i favour c) (with some b)): each development should be forked into a separate branch in the CVS; the core-developpers of this branch work on the code until they consider it stable and then make a call for testing via the list. after it has proven to run stable on all platforms this tree is merged back in.
i would suggest that the releasing should be done on each merge of a development-branch to the main-trunk that adds new functionality. (this can be discussed; it is just fundamentally different from the last release) the main-trunk can be used for bug-fixing...
------------- new features: i'm looking forward to vertex-manipulation, pixel-shaders, multiple gemwins, MMX/SSE2, new pixel-effects, pixel-analysis and tons of other things.
cheers, comments ? and happy coding
mfg.as.dr IOhannes