gregor lingl tdwdqrxylhnaonat hi everyone posting refer paragraph pep 361 says nontrivial feature listed pep must discussed pythondev enhancements include turtlepy replacement enhancements time ago offered xturtlepy replacement supplement turtlepy discussion followed httpwwwpythonorgdevsummary20060616_20060630 europython 2006 gave talk xturtle since quite positive feedback including encouragement offer include python standard distribution quite people including guido van rossum last weeks enhancements xturtle put current version xturtle website download order get feedback api well possible bug reports version still needs code polishing httpwwwrg16atpythonxturtledownloadhtml im interested know still issue initiated procedure decide decision negative things done id continue develop xturtle elsewhere decision positive id able prepare two equivalent versions python26 python3000 within two three weeks port python3000 nearly ready could include say 85 documentation albeit still correct format think examined reviewers also discussion features include include would useful id like intensivly take part discussion development possible decision include xturtle python certainly take place first beta release would enough time polish documentation fix bugs discovery would certainly advantage put prerelease early possible course know xturtle side issue current development efforts unfortunately im familiar procedures needed get new module python kindly ask advice proceed time offering cooperation best regards gregor lingl guido van rossum schrieb python 30 26 coming along really nice optimistic make projected august date final releases 26 30 may remember barry new release manager suggested synchronize releases 26 30 could potentially save release manager assistants time final releases together sends clear signal community versions receive equal support however looking calendar think need little planning management weve typically done python releases final release august means plan release first beta june second one july means time two alpha releases april may im thinking 12 release candidates 12 weeks ahead final release barry make detailed timetable im fine slippage especially planned ahead individual releases due availability release personnel dont want held features bugs unless absolutely dramatic showstopping nature order make tight release schedule try come list tasks need done prioritize include documentation supporting tools like 2to3 include features backports features cleanup bugs whatever else needs done eg bugbot maintenance past weve used shared spreadsheets google purpose seeing havent updated ages im skeptical sufficient tool day job google weve started task management project bug tracker tracker features make particularly easy anyone suggestion online open shared task management system cold adopt bite bullet put everything bug tracker suggestions anythings better email ps realize ive rather absent day day activities python 3000 world lately temporary condition due important impending launch day job expect much time python starting april _______________________________________________ pythondev mailing list zvlllneumpythonorg httpmailpythonorgmailmanlistinfopythondev unsubscribe httpmailpythonorgmailmanoptionspythondevpythondev40tangomucom wed 06 aug 2008 105505 0100 pythondev python3000 26 30 project management