Would it be worthwhile prodding each of the release managers for an update?
It would be nice to see something about 2.6 in the newsletter (roadmap,
timeline, release manager, process enhancements, etc), too, now that 2.5
has hit release candidate. The last dev meeting touched on some of this,
Hi all-
It's time for your blurbs and write-ups! What's going on at your library?
Do you have any development underway? Just brought up a new Evergreen
feature? Any other exciting Evergreen news you'd like to share?
Please send your interesting tidbits my way by Friday October 18th -