From: Jesse Vincent [mailto:jesse@fsck.com] > > ... > > > > > > * Updates to dual-life modules should consist of minimal patches > to > > > fix crashing or security issues (as above). > > > > Any thoughts on what we do for the version numbers of updated dual- > life > > modules, if, say, you want to only take part of a fix that was > applied to > > the CPAN copy of the module? Or to apply a fix that hasn't made it to > CPAN > > yet? > > > To date, we've been bumping version numbers to devel version numbers as > minimally above the released version # as possible. Of course, for > non-code changes (docs or tests), we don't always even do _that_. The only possible problem with using devel numbers is making sure they don't clash with a CPAN devel version. In practice I don't imagine it will be an issue, but it is something to look out for. PaulThread Previous | Thread Next