[Bioperl-l] Re: Next BioPerl release

[Siddhartha Basu]

On Wed, 06 Feb 2013, Fields, Christopher J wrote:

> On Feb 6, 2013, at 1:36 PM, Siddhartha Basu <sidd.basu at gmail.com>
>  wrote:
> 
> > Hi, 
> > 
> > On Tue, 05 Feb 2013, Fields, Christopher J wrote:
> > 
> >> All,
> >> 
> >> I am scheduling the next BioPerl CPAN release tentatively for March 1.  Any help in triaging bug reports would be greatly appreciated!  
> >> 
> >> Amongst all other changes, as mentioned in a separate thread we will remove Bio::FeatureIO, now developed in a separate repository:
> >> 
> >>    https://github.com/bioperl/Bio-FeatureIO
> >> 
> >> Feedback, suggestions, etc are greatly appreciated.
> > 
> > Here are CI build report on 5.12, 5.14 and 5.16 using travis. 
> > https://api.travis-ci.org/jobs/4623997/log.txt?deansi=true
> > https://api.travis-ci.org/jobs/4623998/log.txt?deansi=true
> > https://api.travis-ci.org/jobs/4623999/log.txt?deansi=true
> > 
> > Could not get 5.10 to work on travis. Though i activated the (--network)
> > option,  it still didn't run one of the test that needs network. Also, initially got
> > confused by the fact that though it has dist.ini,  the tests still has
> > to run through Build.PL. Running **dzil test** do not work.
> > 
> > Hope this helps.
> > 
> > thanks, 
> > -siddhartha
> 
> Just to point out, that was for Bio-FeatureIO.  Truthfully I'm not worried about that one yet; got to get over Mt. Everest first (the main release).  
So,  what are steps left for getting the release out to CPAN. Like are
there lot of feature branches still left to be merged,  are there a lot
of unit tests still not passing. Just trying to figure out anyway i
could be of any help to expedite the release process. However,  if they
are already taken care of,  please ignore.

> 
> Build.PL is there mainly as a convenience for users w/o Dist::Zilla, which, last I recall, had a higher dependency list than even BioPerl (though I may be mistaken).  I'll probably have to set up a Build.PL that can be clobbered by Dist::Zilla as needed.  
As far as the error i encountered, presence of Build.PL was blocking dzil
build/release process. And by default,  dzil expects to generate
Build.PL during its build/release process. However,  i am not sure which
mode is the most suitable for bioperl devs.
> Or we can just get rid of it and insist that dev. code has to be added via 'use lib' or PERL5LIB, and not allow installation.

thanks, 
-siddhartha

> 
> chris