Hi,

I'd like to toss my hat in the ring as the Evergreen 3.2 release manager.
I have served as release manager in the past for Evergreen 2.8.  It's been
a little while and the process has evolved, but I look forward to the
challenge.

Evergreen 3.0 and 3.1 marked the transition period from the XUL client to
the browser client.  For 3.2, we'll be saying farewell to the XUL client
[1].  As release manager, my primary goal will be to define the process for
retiring the XUL client and helping to see that process through.  That
will, of course, include confirming that the browser client is fully up to
the task of replacing the XUL client.

Another goal of mine is to solidify a plan for upgrading our version of
AnguarJS to Angular.  This project will span multiple release cycles.  For
3.2, I hope to reach consensus on the upgrade strategy, define a project
time line, and maybe make headway on some of the code changes.

And finally, I would like to do another Feedback Fest this summer.  This is
where everyone, core committers in particular, are asked to review
outstanding pull requests and help nudge them along in a variety of ways.
I found last year's fests [2][3] to be a great way to score a lot of small
victories -- and they add up.

As far as scheduling goes, I would follow examples from releases past, with
a September release, preceded by the various slushes, freezes, betas, and
release candidates.

I'm happy to answer questions.

Thanks,

-b

[1] http://libmail.georgialibraries.org/pipermail/open-ils-d
ev/2017-August/010400.html
[2] https://wiki.evergreen-ils.org/doku.php?id=dev:3.0:feedback_fest_1
[3] https://wiki.evergreen-ils.org/doku.php?id=dev:3.0:feedback_fest_2

On Thu, Apr 5, 2018 at 3:07 PM, Galen Charlton <g...@equinoxinitiative.org>
wrote:

> Hi,
>
> It's now time to decide who will be Release Manager for the autumn
> 2018 release of Evergreen, Evergreen 3.2.
>
> 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, 20 April 2018. Nominations should be made by email to
> open-ils-...@list.georgialibraries.org with a Cc: to
> open-ils-general@list.georgialibraries.org. 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 adhere to the established schedule for the release
> milestones.
>
> If more than one candidate is nominated, an election will be held in
> the #evergreen IRC channel on freenode.net on 25 April 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
> Infrastructure and Added 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
>

Reply via email to
https://www.mail-archive.com/open-ils-general@list.georgialibraries.org/msg14203.html
www.mail-archive.com
crawl=CC-MAIN-2019-51
10675
application/http; msgtype=response
sha1:IHVSEWV2U2IKBDNWLH3YLUSWXHDUHXVC
<urn:uuid:d7cb2816-a880-4f6a-b688-0ba08f1dd02f>
2019-12-11T18:14:42Z
72.52.77.8
text/html
sha1:DDYT2GPAVNYU7JAZESA56LFHGFSIVXVT
<urn:uuid:5a23e8c6-6e37-4e4d-80db-88d1fb3cb238>
https://www.mail-archive.com/open-ils-general@list.georgialibraries.org/msg14203.html
response
<urn:uuid:b3913411-202e-4ea4-8969-317d841c9906>
isPartOf: CC-MAIN-2019-51
publisher: Common Crawl
description: Wide crawl of the web for December 2019
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-9.ec2.internal
software: Apache Nutch 1.16 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.1-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/