I've cut and uploaded two new release tarballs this evening, one for 2.0-RC1 and one for the initial "gold" release of 1.6.2.0. They live in the usual spots, and I'd volunteer to update the website but I've run out of steam and I'm out of town tomorrow.
One note about both of these is that neither contains the fix committed for two documented bugs[1][2]. Both of their upstream branches (trunk and rel_1_6) do, however. I did not feel confident in my standalone testing this close to cutting the releases to include backports for those. As soon as we can confirm (or not) the efficacy of the fixes I will backport them. The revision numbers are listed in the LP bug tickets if you're curious. This will likely cause a 1.6.2.1 in short-ish order, but I don't think it should cause another RC as long as the fixes, as committed, work properly. On a release-related note, I want to say a big "thank you" to everyone that has tested, provided feedback, debugged, patched, documented, improved and generally pitched with EG 2.0 in during this release cycle. There are plenty of rough edges and areas for improvement left in the newest feature sets in Evergreen, but they're significantly smaller and less dangerous than they would have been without all of your help. I'm personally really proud of and humbled by what we've all collectively built, both in terms of the software /and/ an Open Source community. Everyone, have a good Holiday season, and get some well-deserved rest. Please! And, with that, I'm off to get some rest myself. G'night. [1] https://bugs.launchpad.net/evergreen/+bug/693468 [2] https://bugs.launchpad.net/evergreen/+bug/693472 -- Mike Rylander | VP, Research and Design | Equinox Software, Inc. / The Evergreen Experts | phone: 1-877-OPEN-ILS (673-6457) | email: [email protected] | web: http://www.esilibrary.com
