# from David Golden # on Wednesday 14 January 2009 10:52: >> Send an error report immediately after the commit, and the committer >> (who may know exactly what went wrong without looking) will probably >> still be available to fix it. > >What if we moved to a more regular alpha release schedule? That would > get CPAN Testers involved to check things. That's not quite granular > to each commit, but it will speed up the feedback cycle quite a bit.
That would mean more quality at the cost of more eric. Ideally, I would (when wearing my release manager hat once per week) have a green button for "push an alpha" and a green button for "push a release". I can make the buttons, but the information "go for alpha" needs to come from e.g. trunk having passed the tests on a sufficient set of perls+platforms, and the information "go for release" would come from a week or two worth of cpantesters results. At the moment, that information is either missing or very far from being aggregated into even a red light. Is testing against svn commits too difficult? If so, what would make it easier? Note: push notifications are available via: [email protected] --Eric -- If the above message is encrypted and you have lost your pgp key, please send a self-addressed, stamped lead box to the address below. --------------------------------------------------- http://scratchcomputing.com ---------------------------------------------------
