Hello everybody, I want to raise this discussion on public mailing-list, as mingw-w64's release-cycle might be also of interest to some of our users. Right now we do the major-release by gut feeling with a background plan about features new version shall include. Now I got the request to do major release like some other ventures - eg gcc, binutils - after a fixed time-line. For example if we would decide for a one-year release-cycle, it would Mean that we work about 6 - 8 months on new features, then we switch to stabelizing phase for 3 months, and then doing major-version branching and doing just bug-fixing on that branch. Another approach would be to do branching only if we are feature-complete for one version. That of course means we should switch from gut-feeling to more detailed feature-plan.
So I would like to get your opinion. You might have complete different opinion about planning mingw-w64's release-cycles, so don't hesitate to tell us what you think about this subject. Regards, Kai ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct _______________________________________________ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
