guido van rossum hoaufpythonorg tue mar 18 2008 839 barry warsaw wrote mar 18 2008 1211 guido van rossum wrote hm feels bit like inflation priorities would lots critical bugs quite release blockers highest priority pertains upcoming release could weeks future want simple roundup query consult release cycle know whether everythings fine whether start pestering people pull big red stop release button critical gives us priority things really need fix maybe right second sure mild concern terms chosen sound bit alarming b theres term left even alarming issues also want express concern sounds like bit automatic draconian key goal well mine case manage developers get releases cost even though release schedule set stone think send variety reminders ahead scheduled release reminders must come human bot kind consensus comfortable releasing code current state even alpha release thats necessarily expressed showstopper bugs maybe reminder mail could include exhortation create new showstopper issues anything developer feels really addressed release even thought bug release reminder emails act kind wakeup call many developers another little trick using group google bug tracks specific release ive found particularly handy releases done release branches fixes dev branch need cherrypicked want use mailing list thats probably fine id comfortable 12 priorities eg one higher stuff makes buildbot go red ie breaks test two higher stuff affects developers eg stuff checked doesnt even build think neither use cases get far neal talked agreement commit makes buildbots go red breaks build going revert tough luck joe dev please test changes carefully next time sure guido van rossum home page httpwwwpythonorgguido _______________________________________________ pythondev mailing list zvlllneumpythonorg httpmailpythonorgmailmanlistinfopythondev unsubscribe httpmailpythonorgmailmanoptionspythondevpythondev40tangomucom wed 06 aug 2008 081252 0500 pythondev change priority fields