Hello, I know we're all busy, but if the code just sits in a branch, it isn't being tested and that increases the risk of failures later down the road.
I'd like to get these changes out at least in the form of a dev release. That way all interested parties can get access to fixes and we can get feedback quickly. I would like to request co-maint so that I can push more frequent dev releases. This is the same cycle that Perl5 goes through <http://perl5.git.perl.org/perl.git/tags>. The frequent releases of Perl release candidates are made to avoid having the next release of Perl5 breaking all of CPAN. Also, it will become difficult to handle all the new dists post-split if quick dev releases can not be released and tested. Regards, - Zaki Mughal On 2015-07-27 at 15:27:29 -0500, Zakariyya Mughal wrote: > Hello all, > > I was wondering if I could get a code review on these two branches: > > - unmerged-to-master-drop-2.011_01 > <https://github.com/PDLPorters/pdl/pull/123> > - sf390 <https://github.com/PDLPorters/pdl/pull/128> > > You can comment directly on the diff on GitHub if you see anything that > needs work. > > I'm trying to keep the momentum between releases going so that we can > launch into the split very soon. > > Cheers, > - Zaki Mughal ------------------------------------------------------------------------------ _______________________________________________ pdl-devel mailing list pdl-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pdl-devel
