Tuesday, March 17, 2020

MusicBrainz Server update, 2020-03-16 | MusicBrainz Blog

Mostly bugfixes today, along with a new data report, plus usual small improvements, React conversion and refactoring. We also blocked ratings for unverified users, since a specific artist was getting hundreds of ratings by people creating many accounts per person just for that (people, please be nice!).

Thanks to andrybo6, chaban, cyna, dimpole, dseomn, gioele, hibiscuskazeneko, jesus2099, kellnerd, mfmeulenbelt, nikki, outsidecontext, panos, sophist, sothotalker, yindesu, and all others who submitted patches, reported issues, tested beta version, or contributed to translations!

The git tag is v-2020-03-16.

Bug

  • [MBS-7835] – [No lyrics] works showing up as “No linguistic content” in old edit summaries
  • [MBS-9359] – Web service shows “mul” languages, but all single languages are duplicates
  • [MBS-9651] – Top voters overall includes more edits than editor profile’s yes+no+approve
  • [MBS-10628] – [no label] should not be editable
  • [MBS-10633] – Can’t change capitalization on username
  • [MBS-10661] – Recording-work rel not showing pending edits on release page
  • [MBS-10683] – Map doesn’t focus on new marker when creating a new Place
  • [MBS-10684] – Message over Place’s map is misleading
  • [MBS-10685] – Place maps: Zooming by clicking doesn’t follow the cursor
  • [MBS-10693] – Artist merge submission page doesn’t show any error message if you attempt to merge a special purpose artist

Improvement

  • [MBS-4090] – Report for recordings with a single track but with different spellings
  • [MBS-10607] – Give context to translations of “unknown” / “(unknown)”
  • [MBS-10676] – Add MD5/SHA256 checksum files for JSON data dumps
  • [MBS-10695] – Show full language names on work lists

React Conversion Task

  • [MBS-10618] – Convert Edit work edit to React

Other Task

  • [MBS-10671] – Block ratings for unverified users
  • [MBS-10689] – Update MapBox API calls
  • [MBS-10692] – Change React imports to “import * as React”
[from https://ift.tt/2lc8A0P]

No comments: