lp:evergreen/3.13

Branch merges

This import branch has no branches proposed for merge into it.

No branches dependent on this one.

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

27262. By Andrea Neiman on 2024-05-30

Docs: cleanup

Signed-off-by: Andrea Buntz Neiman <email address hidden>

27261. By Andrea Neiman on 2024-05-30

Docs: 3.13-RC release notes

Signed-off-by: Andrea Buntz Neiman <email address hidden>

27260. By Andrea Neiman on 2024-05-30

Docs: 3.13 release note updates

Signed-off-by: Andrea Buntz Neiman <email address hidden>

27259. By Llewellyn Marshall <email address hidden> on 2024-05-30

LP2067640 fix mistake in retrieve coordinates test, added tests for the remaining 3 functions in geo application module

Signed-off-by: Llewellyn Marshall <email address hidden>
Signed-off-by: Jane Sandberg <email address hidden>

27258. By Blake GH on 2024-05-30

Updating relator codes for 3.13

Signed-off-by: blake <email address hidden>

27257. By Blake GH on 2024-05-29

LP#2059974: stamp DB update

Signed-off-by: blake <email address hidden>

27256. By Mike Rylander on 2024-05-29

LP#2059974: Restrict search length for suggestions

Long searches (many words) with few hits can cause performance issues
stemming from the combinatorial effect of suggestion efficacy testing.
IOW, things like full-title searches that match well (and therefore
produce few results, triggering suggestion) can cause cstore and
database backends to spin uselessly.

This commit restricts searches to a three (3) term cap by default when
deciding whether to generate suggestions using the current
single-class/multi-word infrastructure.

The term count limit can be adjusted by changing the value of the Global
Flag called search.max_suggestion_search_terms to be the desired
max-words integer value. If the Global Flag is disabled, the default
value of 3 is enforced.

This is a blunt instrument, but plans for a nuanced replacement are in
place for the next round of Did You Mean development.

Signed-off-by: Mike Rylander <email address hidden>
Signed-off-by: Elizabeth Davis <email address hidden>

27255. By Stephanie Leary on 2024-05-29

LP2067115: More fieldmapper comboboxes domId

Sets the domId attribute on templated fieldmapper editor fields and
components that contain comboboxes. This corrects a mismatch between the
form label's ID and the input's.

Signed-off-by: Stephanie Leary <email address hidden>
Signed-off-by: blake <email address hidden>

27254. By Jane Sandberg <email address hidden> on 2024-05-29

LP2067115: Fieldmapper should set combobox domId, not id

To test:
1. Install an accessibility checking browser plugin like WAVE or Axe (or just use lighthouse on Chrome or Edge)
2. Go to Administration > Local > Carousels
3. Press the New Carousels Button
4. Run your accessibility checker.
5. Note that you no longer get an error about form field
   accessible names

Alternatively, you can run the supplied nightwatch test
from the eg2 directory with:
`MOZ_HEADLESS=1 npx nightwatch nightwatch/src/staff/admin/local/booking/resource.spec.ts`

Release-note: Fix an accessibility issue in staff client forms.

Signed-off-by: Jane Sandberg <email address hidden>
Signed-off-by: Stephanie Leary <email address hidden>
Signed-off-by: blake <email address hidden>

27253. By Blake GH on 2024-05-28

LP#2066981 Stamping upgrade 1417

Signed-off-by: blake <email address hidden>