[vtk-developers] announce: vtk 6.2.0 release candidate 1 is ready
DLRdave at aol.com
Sat Feb 21 20:19:53 EST 2015
Just some real-world data to consider:
For the past three VTK releases (5.10, 6.0 and 6.1), here are the
stats, based on the tags in the git repo.
average number of release candidates before a release's "final"
(x.x.0) release: 3
average number of days between consecutive release candidates: 16
average number of days from rc1 to final release: 40
average number of days between x-rc1 and (x+1)-rc1: 357
I would think such readily available data ought to be considered when
determining the schedule for a set of release candidates. Even by
those whose hair is geometrically challenged. ;-)
Based on historical data, I would expect the final release of VTK
6.2.0 to land around Feb. 16th + 40, or approximately March 28th.
Thanks for the efforts. I am particularly looking forward to the
OpenGL2 backend becoming a reality, even if it is still experimental
for this release.
On Sat, Feb 21, 2015 at 7:45 AM, Will Schroeder
<will.schroeder at kitware.com> wrote:
> There is also the pointy-haired management concern. That is, we are coming
> up to the end of Year 2 NIH funding for VTK Maintenance. We have a report
> due in mid-March and I want to make it as strong as possible so we can
> continue doing other great work along the lines of OpenGL2, interaction,
> community, and medical data integration. Being able to talk about a release
> makes me very happy, and it will honor the investment that NIH is making
> into VTK.
> On Fri, Feb 20, 2015 at 9:09 AM, Marcus D. Hanwell
> <marcus.hanwell at kitware.com> wrote:
>> On Thu, Feb 19, 2015 at 4:47 PM, Sean McBride <sean at rogue-research.com>
>> > On Thu, 19 Feb 2015 16:36:12 -0500, Marcus D. Hanwell said:
>> >>Why make more than one RC if there are no
>> >>critical flaws discovered?
>> > No disagreement there. But if the 1 rc period lasts only 4 business
>> > days (it was announced late Monday), there's *insufficient time* to look for
>> > flaws.
>> Agreed, I have been really busy with other things and didn't
>> appreciate this. Hopefully we can extend it out a day or two - would
>> that offer enough time?
>> > VTK 6.1 was released 13 months ago. Why the rush to declare 6.2 final?
>> These things are always a balancing act, and we would like to increase
>> the release frequency so that we avoid this 13 month cycles. Thanks
>> for your feedback, and all of your contributions to VTK.
>> Powered by www.kitware.com
>> Visit other Kitware open-source projects at
>> Search the list archives at: http://markmail.org/search/?q=vtk-developers
>> Follow this link to subscribe/unsubscribe:
> William J. Schroeder, PhD
> Kitware, Inc.
> 28 Corporate Drive
> Clifton Park, NY 12065
> will.schroeder at kitware.com
> (518) 881-4902
> Powered by www.kitware.com
> Visit other Kitware open-source projects at
> Search the list archives at: http://markmail.org/search/?q=vtk-developers
> Follow this link to subscribe/unsubscribe:
More information about the vtk-developers