Hello all,

Evergreen 3.15.4 and 3.14.9 are due to be released on Wednesday, August 20.
I generally have been putting a call out at the developers meeting, but I
will be out of town during that part of next week.

So, the call is going out today to ask for volunteers to help with these
releases. We currently need people to help with translations, building and
testing the tarballs, and uploading "the things." If you are willing and
able, please add your name/handle to the BuildMaster Coordination
spreadsheet
<https://docs.google.com/spreadsheets/d/1aKffVGU_vIWbtFR_vpoHsqodSw-Kdd5yn65RpfkMKKA/edit?gid=0#gid=0>.
A wrangling email will go out on Thursday or Friday of next week (Aug. 14
or 15).

Also, in case you have the time/access/interest, there are currently 37 LP
tickets with signoffs
<https://bugs.launchpad.net/evergreen/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=DEFERRED&field.status%3Alist=FIXCOMMITTED&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.milestone%3Alist=103023&field.milestone%3Alist=103024&field.tag=signedoff&field.tags_combinator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on&search=Search>
for
3.14.9 and/or 3.15.4 but only two with fixes committed.

Thanks all for making Evergreen ILS awesome,

*Ruth Frasur Davis, Coordinator*
*Evergreen Collaborative Development Initiative*
https://evergreencdi.org
(765) 580-1137
_______________________________________________
Evergreen-dev mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to