Dear Evergreen Community,
I am writing to offer myself as release manager for the upcoming 3.0 release.
Our library is an independent academic installation, and having recently
celebrated 7 years on Evergreen, a fairly early adopter. I served as release
manager for 2.5 and 2.6, release cycles
[I apologize for possible duplication; my calvin.edu email is getting
"greylisted" by the mailing list, so I am sending this a second time from
Gmail.]
Dear Evergreen Community,
I am writing to offer myself as release manager for the upcoming 3.0
release.
Our library is an independent academic
Hi,
It is fast approaching time to elect the Release Manager for the next
Evergreen release.
The Release Manager does not have to be a core committer, but does
need to be familiar with Git and have already contributed
substantially to the Evergreen project whether it be code or
documentation.
