* [Tux] thinks about creating a short ticklist for "What do I do before a release" <[Tux]> xdg, if we take all the "What should we do" in the three river sections <[Tux]> and create an "action" for each of those with suggested modules to support that "best-practice" <[Tux]> module authors can use it to check every point, still haveing the freedom to ignore any of the points <[Tux]> [v] make test <[Tux]> [v] check spelling <[Tux]> [ ] check Changlog <[Tux]> [ ] check upstream <[Tux]> [ ] check downstream <[Tux]> etc etc <[Tux]> Module::Release, Test::*, Pod::Spell::CommonMistakes, Text::Aspell, ... <BooK> Tux: so the policies can be partly expressed in code... * [Tux] is preparing a new Text::CSV_XS release <[Tux]> and the test process by now takes so long I tend to forget steps <[Tux]> first test with 105 versions of perl <[Tux]> then test on all available OS's <[Tux]> then performance tests <[Tux]> etc etc <[Tux]> then downriver tests <[Tux]> a T::CXS release takes a complete working day
https://github.com/Tux/Release-Checklist started as a first brainfart any takers for co-maint? -- H.Merijn Brand http://tux.nl Perl Monger http://amsterdam.pm.org/ using perl5.00307 .. 5.21 porting perl5 on HP-UX, AIX, and openSUSE http://mirrors.develooper.com/hpux/ http://www.test-smoke.org/ http://qa.perl.org http://www.goldmark.org/jeff/stupid-disclaimers/
pgpMUAzsWN875.pgp
Description: OpenPGP digital signature
