guido van rossum hoaufpythonorg 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 guido van rossum home page httpwwwpythonorgguido _______________________________________________ pythondev mailing list zvlllneumpythonorg httpmailpythonorgmailmanlistinfopythondev unsubscribe httpmailpythonorgmailmanoptionspythondevpythondev40tangomucom wed 06 aug 2008 043717 0500 pythondev 26 30 project management