On Thursday 14 May 2009, Zach Welch wrote: > If you are still willing continue in this role, I would like to see you > document the release processes (perhaps in doc/manual/releases.txt?) and > inform the rest of us what we need to do to make 0.2.0 a reality.
Heck ... even if you're not willing, I suspect you're the best person to write a brief "how to get a release out" email! Not for incorporation into the Doxygen manual, but to help kickstart the 0.2 release. Surely there are two or three specific things the "community" should do better next time... My own 0.2.0 (?) questions cover the basics: - Who will oversee it? - What will it include? - When do we want it? - How will it happen? - Why do we even need/want it? Re "Why", IMO it might suffice to say that after four or five months, lots of bugs have been fixed and features added, so it's just time to clean up the rough spots and declare victory over some stable code. - Dave _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
