<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<br class="">
<div>
<blockquote type="cite" class="">
<div class="">On Jun 27, 2016, at 8:48 PM, James E Keenan <<a href="mailto:jkeen@verizon.net" class="">jkeen@verizon.net</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class=""><span style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">Unfortunately,
this opportunity was not seized. YAPC::NA::2016 -- now re-branded as The Perl Conference 2016 -- has come and gone. During the Pull Request Challenge which was part of the conference, I did create one p.r. against BioPerl, which I'm glad to say has been
accepted. However, we would have been in a better position to advocate for non-bio-focused Perl programmers to help with BioPerl if we had had an up-to-date CPAN release.</span><br style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<br style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<span style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">(By
the way, I heard two presentations at the conference that dealt with genomic data.)</span><br style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<br style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<span style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">Since
AFAICT your github 'master' branch is passing all tests, I would urge you to simply increment the $VERSION numbers by .001 throughout and upload to CPAN. After that's done, you can discuss whether or not you want to call the next version 1.6 or not.</span><br style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<br style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<span style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">Thank
you very much.</span><br style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<span style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">Jim
Keenan</span><br style="font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
</div>
</blockquote>
<br class="">
</div>
<div>Jim,</div>
<div><br class="">
</div>
<div>Though some might consider it a bit pushy we do appreciate the nudge on releases. I was simply not able to fit this into my schedule, which has become much busier over the last few years. We also had a major site migration due to a hacked server that
forced our hand prematurely, which really didn’t help much.</div>
<div><br class="">
</div>
<div>Saying that, simply pushing out a new 1.6.x is not tenable off the master branch; you will note that we had long ago created a separate release branch for 1.6.x, which has been highly cherry-picked to. We will be releasing a 1.7 release from 'master'
once we have addressed a few minor factors (<a href="https://github.com/bioperl/bioperl-live/issues/158" class="">https://github.com/bioperl/bioperl-live/issues/158</a>). It’s possible some may be added such as cleaning up access for remote databases, which
are not run by default but fail due to changes outside our control. You’ll also note this hasn’t been announced to the list yet :)</div>
<div><br class="">
</div>
<div>Also, if anyone, including you Jim, want to participate in development to improve BioPerl, I am more than happy to have you on board (you will also note I have the bioperl6 repo as well, which I will likely switch over to the ‘bioperl' organization account).
I have been pretty free about giving out perms for commits to the Github repo for anyone who wants to contribute. We generally have a few people as release managers though the releases over the last several years have been predominately by me. I have taken
the steps to add two new co-maints to the project, both of whom have long been members of the BioPerl community, who can help act as release managers for future releases.</div>
<div><br class="">
</div>
<div>Thanks,</div>
<div><br class="">
</div>
<div>chris</div>
<br class="">
</body>
</html>