[vtk-developers] development roadmap?

[Will Schroeder]

Hi Michael-

There are important points here. I can understand the difficulty of keeping 
up with a moving target. As you say, we can help you help us; although I 
think part of what you are saying is that there should not be a "you" and 
"us", just an "us".

Would a single web page, something like a "Developers Page", with current 
version information, a road map, proposed changes, and pending changes, be 
something that might work? It sounds like we need information (maybe a 
variant of the style guide) which indicates the current process for 
creating a class.

What do you think would be the appropriate number of mini-releases per 
year? How do you see numbering them?

I'm concerned about freezing the CVS repository. Would might happen is that 
instead of a torrent of changes, you'd have a series of floods each time 
the gates were opened. These impulse functions create a lot of dynamics... 
Maybe we could do short freezes around the releases....make use of code 
branches more.

I'm thinking about it....

Will