On 10/02/13 09:24, Gabor Szabo wrote: > Hi, > > I just looked at http://changes.cpanhq.org/dist/Padre that tells me > the Changes file does not > match the CPAN::Changes standard. I concur > As I can see we have our odd version numbers with the line > Development version, not released > instead of the date. I agree a date would be nice addition > > I know the odd numbers are used during development, but I wonder why > do we keep them > in the changes file when we release Padre? It's called a history trail, I think :) > > Wouldn't it be better to remove the odd lines and unite their content > with the version I am now confused :( > where they were really released? > > 0.97 Development version, not released > 0.95 Development version, not released > 0.93 Development version, not released > 0.91 Development version, not released > 0.89 Development version, not released > 0.87 Development version, not released > 0.85 Development version, not released > 0.83 Development version, not released > 0.81 Development version, not released > 0.79 Development version, not released > 0.77 Development version, not released > 0.75 Development version, not released > 0.73 Development version, not released > 0.71 Development version, not released > > > Gabor > _______________________________________________ > Padre-dev mailing list > Padre-dev@perlide.org > http://mail.perlide.org/mailman/listinfo/padre-dev > Should this not just be a feature enhancement ticket, to make our Changes file comply with -> https://metacpan.org/module/CPAN::Changes::Spec
just as see - http://padre.perlide.org/trac/browser/trunk/Padre-Plugin-Git/Changes also - http://changes.cpanhq.org/dist/Padre-Plugin-Git do regards bowtie _______________________________________________ Padre-dev mailing list Padre-dev@perlide.org http://mail.perlide.org/mailman/listinfo/padre-dev
