Hello all, Based on the feedback I have received, the cutoff for targeting bugs at 2.6.0-beta1 will be *Tuesday, February 11 at noon EST*. At that time, I will create both an RC milestone (for new bugs) and an Evergreen-next milestone (for new features not getting into 2.6). Please do not assign any bugs to the beta1 milestone after noon on Tuesday.
After the cutoff on the 11th, the community will have until *end-of-day on Tuesday, February 18* to review and commit the beta-targeted bugs. The following day I will begin (and hopefully finish) the process of cutting a 2.6.0 beta release. On a related topic, earlier today I went through all the unfinished bugs for 2.6.0-alpha1. Most were moved to 2.6.0-beta1, but a few were not. If a bug had no pullrequest, and no signs of life, I likely set it back to being untargeted. Please look over the list of bugs before the February 11 cutoff and make sure bugs you want included in 2.6 are targeted. The current list can be seen here: https://bugs.launchpad.net/evergreen/+milestone/2.6.0-beta1 As always, questions, comments, and concerns about the release process are welcome. Thanks, Dan Daniel Wells Library Programmer/Analyst Hekman Library, Calvin College 616.526.7133
