On Friday 02 September 2005 02:16, Noel J. Bergman wrote: > But the point of the > comment you quoted is that we should be basing release on something stable > and tested, not trying to cut a release from a rapidly moving target. > I don't really have a say in this, but i do disagree somewhat. The code will be stable (feature wise) the moment no new feature are added. So you could create a 2.3.0 branch right now and call it 'stable' (again feature wise). The just release 2.3.0a1 and start testing. Work out the bugs from there and call it final when the bugs are out of it. Work on new stuff can just go on in the trunk even during when it's release time.
That's, imho, how 'Release early, release often' works. In a more extreme form it's even possible to simply decide there will be a new release each x months. I don't really have the insight in the James community to make a proper judgement about this, but i do think more frequent releases may help James to gain some momentum and may also speed up development because there will be more user testing. Greeting, Arjan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
