So we could do this for 1.84, the next release. If sombody is about to submit a major patch let me know and we will wait for that.
On Aug 21, 4:55 am, Phyo Arkar <[email protected]> wrote: > thats good. > > also what i saw at ipython mailing list , when they go into feature freeze , > they call for all contributors / plugin contributors for bug-squishing and > stabillity fixes .Contributors of New features are asked if their works > confident to included the stuff into main stable release. > > On Sat, Aug 21, 2010 at 4:10 AM, mdipierro <[email protected]> wrote: > > yes and no. > > > For example Michele just send me a new gluon/contrib/login_methods/ > > oauth10_account.py which provides OAuth 1.0 authentication. It did not > > affect anything else in web2py and I see no reason from freezing > > adding features like this. > > Mariano is working on a PDF library for web2py. Same argument applies. > > > I see a lot of value in > > > - bug-squishing-contest , > > - Stress test, Test everything , try to crash web2py etc. > > - fix bugs, fix performance issues , improve performance > > - code cleanup , documentation. > > > we can set deadlines for that. This means we would stress test and > > improve features existing at a certain date and we would only add new > > features tagged as "experimental" that do not interfere with parts > > that are being stress tested. Makes sense? > > > Massimo > > > On Aug 20, 3:54 pm, Phyo Arkar <[email protected]> wrote: > > > Like some projects , (what i saw is KDE4) should we go into Feature > > Freeze > > > period? > > > > Well lets say , when web2py hit 1.90 version , stop developing about new > > > features and we will go into > > > -bug-squishing-contest , > > > -Stress test, Test everything , try to crash web2py etc. > > > -fix bugs, fix performance issues , improve performance > > > -code cleanup , documentation. > > > > For a month (or any period) > > > > after that we will get a Stable (Production/Mature) version of web2py. > > > > how that sounds?
