Dear Evergreen Community, After some consideration, I am writing to offer myself as release manager for 3.3.
Our library is an independent academic installation, and will be live on Evergreen for 9 years this December. I served as Release Manager most recently for 3.1, and previously for releases 2.5 and 2.6. In addition to my RM experience, I have also been part of the Buildmaster team since 2.11. My general experience in attempting to *plan* releases has not always turned out, so my goal this time around would be to focus on the fundamentals of managing a release. I will review what I can, code where I must, and encourage and cajole as necessary to move the project forward. As I am seeking a position of at least some small influence, it may also be worth knowing where my personal interests lie in Evergreen development. First, we've taken a good first step into modern Angular, but we will need to remain diligent. Wrapped up with that will also be necessary changes to our translation infrastructure. Second, though sometimes messy and unglamorous, we must still make serious attempts to clean up dead and dying code in our codebase. Some areas there are obvious (XUL), but others tend to build up unnoticed, and can be very frustrating to discover when trying to troubleshoot certain bugs. As far as timeline, I'll keep it simple: 2/20/19 - Feature freeze 2/27/19 - Beta release 3/20/19 - Release Candidate 3/27/19 - Final release I think the feature freeze / beta separation is a little different than what we've planned to do in the past, but I also think it is a little more realistic than saying that the feature freeze date *is* the beta release date. That tends to make for either a pretty unstable beta, or a late release of the actual beta, take your pick :) Thank you for your consideration. Sincerely, Dan On Mon, Oct 15, 2018 at 5:43 PM Galen Charlton <g...@equinoxinitiative.org> wrote: > Hi, > > It's now time to decide who will be Release Manager for the spring > 2019 release of Evergreen, Evergreen 3.3. > > 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. > > Nominations (including self-nominations) are due by 11:59 PM EDT on > Friday, 26 October 2018. Nominations should be made by email to > open-ils-...@list.georgialibraries.org with a Cc: to > email@example.com. Replying to all on this > email will also work. > > Nominees should send an email to both of the above mailing lists a > statement about their relationship to the Evergreen community and > their goals for the next release. The elected release manager will be > expected to follow the typical schedule for a spring release but > should provide information on when they intend to set specific > milestones such as the beta release. > > If more than one candidate is nominated, an election will be held in > the #evergreen IRC channel on freenode.net on 31 October at 15:00 EDT > / 12:00 PDT. > > Everyone is invited to participate in the voting. Evergreen core > committers who cannot make the meeting may submit their vote via email > to the open-ils-dev mailing list. > > Regards, > > Galen > -- > Galen Charlton > Implementation and Services Manager > Equinox Open Library Initiative > phone: 1-877-OPEN-ILS (673-6457) > email: g...@equinoxinitiative.org > web: https://equinoxInitiative.org > direct: +1 770-709-5581 > cell: +1 404-984-4366 >