On Tue, 2009-11-17 at 09:42 +0100, Øyvind Harboe wrote: > On Tue, Nov 17, 2009 at 9:35 AM, Zach Welch <[email protected]> wrote: > > On Mon, 2009-11-16 at 18:01 -0700, David Brownell wrote: > >> On Monday 16 November 2009, Zachary T Welch wrote: > >> > As suggsted by the first commit message, the final act will involve > >> > the removeal of the migration macros; however, that should wait > >> > until we near 1.0, in the event that further migration is required. > >> > >> What would you think makes a release deserve to be called "1.0"? > > > > Basically, we need to run out of our list of "things to fix". That list > > is so long at present that I cannot fathom the code reaching 1.0 for at > > least another year of development. Or to be blunt: When It's Done. > > The lack of TODO items will justify it, so not anytime soon. > > > > Anything less than that, and it'd be little more than marketing hooey. > > The code is being cleaned up at a frantic pace these days, which is > great. When do you see that tapering off?
0.42.7 or so.... :) More directly: I don't. > Minimally for the 0.4 release we'll have to wind down before Xmas sometime... Of course! This kind of development should occur at the beginning of release cycles, tapering off for each release cycle. However, it can still happen in a local branch, on which I based my previous assessment. --Z _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
