On Monday 09 July 2007 14:31, Paul McNett wrote: > A "stable" release simply means that it isn't going to change. > "unstable" is the trunk. It isn't a sore subject (at least not from my > POV), but I'm sure it'll all make more sense after we are post-1.0. > But it does not mean that to me. It (stable) means a working copy with well understood issues to be addressed in the next version. The key words are "working copy". I don't think I'm alone in this understanding. > Our release strategy follows that of other open source projects, > including that of Python itself. There's a set of prior stable releases, > such as Python 2.5, and then there are the development releases, such as > Python 2.6a1. The only thing we are missing is a beta/rc cycle prior to > making a stable release. I assume we'll formalize that post-1.0
Yes I agree post 1.0 things will change. -- John Fabiani _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev Searchable Archives: http://leafe.com/archives/search/dabo-dev This message: http://leafe.com/archives/byMID/dabo-dev/[EMAIL PROTECTED]
