I'm not trying to suggest any particular ongoing testing methodology. I'm just saying that if it's broken now, and we need to test it widely now, lets do a one-off dev release now and you guys can work out a more permanent thing later...
> cd Module-Build > ppi_version change 0.31011 0.31012_01 > svn commit > perl Build.PL > perl Build > perl Build makedist Give me 6 months and I'll automate it in Padre for you... Or something... Adam K 2009/1/15 Eric Wilhelm <[email protected]>: > # from Adam Kennedy > # on Wednesday 14 January 2009 06:52: > >>As soon as there's a packaged tarball living at an arbitrary URL, any >>Strawberry machine can trivially just run the following to test it. >> >>pip http://url... >> >>Pack up a dev release and get the whole repository/branch thing out of >>the picture. >> >>Throw the dev release at CPAN, and the URL at #win32 and #padre, and >>you'll get an answer for "does it work" in a few hours. > > Please relay these instructions to Schwern, as his commit was the one > that done it ;-) > > I already package alpha tarballs and ship them several days ahead of the > release, then manually nag people to manually test that. David's > run-throughs are particularly helpful in finding regressions, and > assuring that we're not going to be surprised by some distro suddenly > failing after the release. > > But that process is already more work for me, including remembering to > check whether we're ready for a release or need to apply a patch and > try again.
