The one good thing about my only job around here being to dump out a release every couple of months was that it was easy to keep the schedule. I had little invested in any particular release, and didn't care much. It's time. Dump it.
Now that I'm getting into a development frame of mind again, I've already scrapped one release, and December is coming up really fast. I'm working on an ambitious project at the moment where my requirements document is already up to four pages and I haven't even gotten into prototypes yet. This is what I design the prototypes from, and then I have to write the code to build it all. Personally, I'm inclined to just stop releasing until I'm good and well ready to push my new stuff out, and make the thing a big shiny feature release full of new bugs and a complete lack of testing. If anybody disagrees, now is the time to pipe up. Maybe I'm losing sight of the trees for the forest here, and I should release some important bug fixes and so on way before potentially February. I can't do everything at once, and right now, I'm not thinking about releases at all. The release manager is on sabbatical indefinitely. Back to my requirements document. (I'm keeping it offline, because my connection to the world has been severely unreliable lately, and I could very well get hung with no access to the wiki.) -- D. Michael McIntyre ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
