I feel we have be cautious with 'getter done' Each time we add some capability time is needed to properly find bugs and update screens configuration wizards etc. We are notorious for waiting waaay too long to make a stabilization branch and so feel compelled to release it too early. Particularly the configuration wizards always have bugs that show themselves right after release. Since we historically only build a ISO once - we are stuck with buggy software for newbees to endure till they update.
I would suggest we have already started to go too far with the inclusion of python 3 code work. Our 2.8 stabilization branch should probably be made under that and soon. Then we should stabilize for a long time like 4 -6 months. Then we should release in another year because there is lots to add in that year. And that is when reverse run should go in. My 2 cents Chris M ________________________________ From: Rod Webster <[email protected]> Sent: May 21, 2019 4:22 AM To: EMC developers Subject: Re: [Emc-developers] Introduction and a couple of questions Well forum member PhillC has a working version of Reverse run in his git repository <https://github.com/phillc54?tab=repositories> and enough people have been using it to confirm it works without breaking anything. Aside from some simulations and one component (plasmac.comp), incorporating reverse run is the only change Phill has done to the core code and he keeps it up to date with master branch weekly. I think he's kept the sims and component separate from his modified master branch code. So there is not really any excuse to leave Reverse run out. Get it done Andy! _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
