Release::Checklist

* [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/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQEcBAEBAgAGBQJVYZwiAAoJEAOhR6E+XcCYuR8H/j6fPM7hVvFxEyZFTg6j5+KX
BmMorUxy2UqM9lXZtBdspe9PWkHb74TzfQR3X6vN5OjuoTzDmYVSeIrDrDaApmm8
M++6xtjlcOxN5Jw/2CCOZYNLV/P7oQCkn77aCFC1AO7SiwM7t7mWW/TxDbYdmB7E
jvWnOcYNcNoFCt2ivLcs4q0GI81x/+IwmNbTd6Wohc864tKvaQf90IJKAsymgimh
m3PYsA0F9++X+xP3e2EEo0JalMvfo5X0KXJ8cHyHREFRNSt5db/k0NDWcZYzzlX3
czjyovST1Nm+b4oxgooONtiERddX37O3h2Uxez85iA4pA8UP530fBNb7mZ2+TXc=
=hpA6
-----END PGP SIGNATURE-----