stable/development release ideas (was : Re: A group in Norway...)

[nick . smethurst]

One idea would be to implement an extreme programming development style where
testing code indicates any instabilities/compile problems. VTK uses this
technique and it works very well. Their official releases are thus rather
arbitrarily and are not determined by the traditional alpha/beta/RC/release
schedule.

Quoting Dirk Eddelbuettel <address@hidden>:
> Yep, the gap between 2.0 and 2.1 is so big that I'd be surprised if
> anyone
> wanted to look after the old one.