stephen j turnbull xjzvfpwxemacsorg speaking barry anyone else explanation understand process welcome scott dial writes dont understand alpha releases supposed serve alpha test internal comprised tests developers working product andor affiliated qa department imagine similarly alpha release developers im sure developer outside core community would want work something missing key features released fairly arbitrarily developers outside core community targeted said know key features missing part point release says stuff working want key feature part stuff key feature given feature download give team feedback early possible lacking dont next alpha presumably roles reversed point dont know developer wouldnt checkout svn case certainly going help root bugs would like using trunk possible fear alpha 2 weeks old start saying please check still problem trunk software development practice matter take two steps back three steps forward point alpha release checkpoint regression temporary feature introduced new development latter admissible trunk goal none one alpha next words bug introduced new development fixed next alpha cant developer misjudged timing merge mainline wasnt ready yet mild concern effects checkins individuals either trying meet deadline even wait alpha release checkin large change im sure happen releases scheduled without feature milestones attached certainly changes environment work done scheduling feature milestones assumes people put priority features given time barry cant assume yet rhythm established barry start asking people start volunteering milestone commitments given releases think probably desirable put deadline pressure individuals rush get work cause alphato alpha regressions advised wait future similar circumstances rhythm established people expect alphas consistently increasing features consistently decreasing defects thats true somethings wrong process team needs step back something nature software development monotone improvement something want even impose trunk points time _______________________________________________ pythondev mailing list zvlllneumpythonorg httpmailpythonorgmailmanlistinfopythondev unsubscribe httpmailpythonorgmailmanoptionspythondevpythondev40tangomucom wed 06 aug 2008 095032 0900 pythondev code freeze