<p dir="ltr">Chris, I don't think it's a problem calling this a developer release. I think we want to get all the myriad patches now in master out and see what people think, in addition to a split. (We are talking about making the split, right? )<br></p>
<p dir="ltr">Brian, first thing would be to do the mutually exclusive dependency grouping exercise for real, my (and others prob) thought has been this may indicate the natural package clumps. I have some scripts that can do this and also could help create the appropriate package metadata, which is a btch to do by hand, but I think must be done.</p>
<p dir="ltr">If we decide now to release using the group PAUSE id, then we can extend the rollout and give Chris a break. Let's make the first installment the group of mods that includes Bio::Seq and friends. This will be a basic dep for almost everything else. <br>
</p>
<div class="cm_quote" style=" color: #787878">On Fri, May 27, 2016 at 10:39 AM, Fields, Christopher J <<a href="mailto:cjfields@illinois.edu">cjfields@illinois.edu</a>> wrote:</div><br><div id="oldcontent" style="background: rgb(255, 255, 255);"><blockquote style="">
<div class="">I can set some time aside later today and this weekend to start on this but we’ll need to go through the process over until we can retrieve the old wiki content. We may just go ahead and pull the trigger on a 1.7 release unless we *really* need
a new 1.6.x. My only concern with odd-numbered releases w/ bioperl tend to worry folks as they have long been noted as developer releases.</div>
<div class=""><br class="">
</div>
<div class="">Long-term, what I suggest is (while I’m working on this) we set up a few others under the BIOPERLML PAUSE umbrella ID so we can spread the load a bit more. My day-to-day schedule has been horrendous, so this would definitely help.</div>
<div class=""><br class="">
</div>
<div class="">Re: documentation: there was a page on releases on the old wiki, now off-line; since the OBF web server compromise we’ve managed to get dumps of all OBF sites (I still need to upload those to the cloud account). </div>
<div class=""><br class="">
</div>
<div class="">chris</div>
<br class="">
<div>
<blockquote class="">
<div class="">On May 27, 2016, at 9:22 AM, Brian Osborne <<a href="mailto:bosborne11@verizon.net" class="">bosborne11@verizon.net</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
Mark,
<div class=""><br class="">
</div>
<div class="">Can you start this list on what needs to be done?</div>
<div class=""><br class="">
</div>
<div class="">BIO</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
<div class="">
<blockquote class="">
<div class="">On May 27, 2016, at 10:13 AM, Mark A Jensen <<a href="mailto:maj@fortinbras.us" class="">maj@fortinbras.us</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<p dir="ltr" class="">I've done some work and thinking (I.e., stewing) about this, if you want help Chris.</p>
<div class="cm_quote" style=" color: #787878">On Fri, May 27, 2016 at 10:07 AM, Brian Osborne <<a href="mailto:bosborne11@verizon.net" class="">bosborne11@verizon.net</a>> wrote:</div>
<br class="">
<div id="oldcontent" style="background: rgb(255, 255, 255);" class="">
<blockquote style="" class="">
<p dir="ltr" class="">Chris,</p>
<p dir="ltr" class="">You are still the de facto leader for CPAN releases, but that does not mean that you have to do all the work. But I think you probably have the most comprehensive view of what needs to be done so I suggest - if we want to get out a release
before YAPC - that you list here what needs to be done. Then we’ll put these into Github, sort out who does what, this worked for the Wiki -> GitHub pages tasks.</p>
<p dir="ltr" class="">Thanks again,</p>
<p dir="ltr" class="">Brian O.</p>
<p dir="ltr" class="">> On May 26, 2016, at 8:47 PM, James E Keenan <<a href="mailto:jkeen@verizon.net" class="">jkeen@verizon.net</a>> wrote:<br class="">
> <br class="">
> On 05/16/2016 09:52 AM, Fields, Christopher J wrote:<br class="">
>> Thanks Jim! We can work on pushing out a new release.<br class="">
>> <br class="">
>> One of the long-term problems with BioPerl is the large size of the distribution; we’ve been considering a new 1.7x series to deal with this, but it’s clearly slowed down over the years. Maybe this will help stimulate that effort again.<br class="">
>> <br class="">
>> chris<br class="">
>> <br class="">
>>> On May 15, 2016, at 6:41 PM, James E Keenan <<a href="mailto:jkeen@verizon.net" class="">jkeen@verizon.net</a>> wrote:<br class="">
>>> <br class="">
>>> [snip]<br class="">
> <br class="">
>>> Your last CPAN release was in July 2014. I strongly advise that you do a CPAN release of BioPerl ASAP so that your project does not suffer reputational damage from all those test failure reports. At the same time, I urge you to go through the bug reports
at <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__rt.cpan.org_Public_Dist_Display.html-3FName-3DBioPerl&d=CwMFaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=fbHa8Njtvh9VmSnzJxiEUTW9NWDwMMwQAzhgZDO41GQ&m=ASh8D2kHlj-3SXVj3DM4iJWuWTPu8T5rBEgXEkaeY7Q&s=Nz6xnaLCX_p9G8jXXgKz4ybAuhnFuSrQEGQEnwP2tYg&e=" class="">
https://rt.cpan.org/Public/Dist/Display.html?Name=BioPerl</a>. It's likely that HEAD on github resolves some of these.<br class="">
>>> <br class="">
>>> Thank you very much.<br class="">
>>> Jim Keenan<br class="">
> <br class="">
> I'd like to follow up on my recommendation that you try to get a new CPAN release of BioPerl out soon.<br class="">
> <br class="">
> The major North American Perl conference, The Perl Conference/YAPC::NA::2016, will be held in Orlando, FL, starting just 26 days from now.<br class="">
> <br class="">
> <a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.yapcna.org_yn2016_&d=CwMFaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=fbHa8Njtvh9VmSnzJxiEUTW9NWDwMMwQAzhgZDO41GQ&m=ASh8D2kHlj-3SXVj3DM4iJWuWTPu8T5rBEgXEkaeY7Q&s=kmKD7Jir7nJjqg1TBsG9bZmXvaJkk1qL5Ehzr9_LHOA&e=" class="">
http://www.yapcna.org/yn2016/</a><br class="">
> <br class="">
> A CPAN release before YAPC would be a strong shot in the arm for the visibility of BioPerl within the larger Perl community. Apart from the fact that there are software engineers who work in the biomedical sciences who frequently attend YAPC, there are also
Perl people (like myself) who are in a position to submit patches and pull requests simply for the purpose of improving the quality of the Perl code. But people in the latter category are unlikely to contribute patches unless they think that there is a realistic
chance of the code's being released to CPAN.<br class="">
> <br class="">
> So, please take advantage of this time-limited opportunity.<br class="">
> <br class="">
> Thank you very much.<br class="">
> Jim Keenan<br class="">
> _______________________________________________<br class="">
> Bioperl-l mailing list<br class="">
> <a href="mailto:Bioperl-l@mailman.open-bio.org" class="">Bioperl-l@mailman.open-bio.org</a><br class="">
> <a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__mailman.open-2Dbio.org_mailman_listinfo_bioperl-2Dl&d=CwMFaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=fbHa8Njtvh9VmSnzJxiEUTW9NWDwMMwQAzhgZDO41GQ&m=ASh8D2kHlj-3SXVj3DM4iJWuWTPu8T5rBEgXEkaeY7Q&s=KKo8zqU4bkEC4Y5tYFw4lV85q_cL2Ft2ETk-i6UkLD4&e=" class="">
http://mailman.open-bio.org/mailman/listinfo/bioperl-l</a><br class="">
</p>
<p dir="ltr" class="">_______________________________________________<br class="">
Bioperl-l mailing list<br class="">
<a href="mailto:Bioperl-l@mailman.open-bio.org" class="">Bioperl-l@mailman.open-bio.org</a><br class="">
<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__mailman.open-2Dbio.org_mailman_listinfo_bioperl-2Dl&d=CwMFaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=fbHa8Njtvh9VmSnzJxiEUTW9NWDwMMwQAzhgZDO41GQ&m=ASh8D2kHlj-3SXVj3DM4iJWuWTPu8T5rBEgXEkaeY7Q&s=KKo8zqU4bkEC4Y5tYFw4lV85q_cL2Ft2ETk-i6UkLD4&e=" class="">http://mailman.open-bio.org/mailman/listinfo/bioperl-l</a></p>
</blockquote>
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
</div>
</div>
</blockquote>
</div>
<br class="">
</blockquote></div>